From mboxrd@z Thu Jan  1 00:00:00 1970
From: Richard G Riley <rileyrgdev@googlemail.com>
Subject: clarification about org-mode
Date: Fri, 12 Oct 2007 01:49:36 +0200
Message-ID: <jmhckxrz3j.fsf@home.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Ig7ml-0002en-1V
	for emacs-orgmode@gnu.org; Thu, 11 Oct 2007 19:49:47 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Ig7mi-0002bt-QB
	for emacs-orgmode@gnu.org; Thu, 11 Oct 2007 19:49:45 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Ig7mi-0002bd-Eb
	for emacs-orgmode@gnu.org; Thu, 11 Oct 2007 19:49:44 -0400
Received: from nf-out-0910.google.com ([64.233.182.187])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <rileyrgdev@googlemail.com>) id 1Ig7mi-0008UV-3F
	for emacs-orgmode@gnu.org; Thu, 11 Oct 2007 19:49:44 -0400
Received: by nf-out-0910.google.com with SMTP id f5so649320nfh
	for <emacs-orgmode@gnu.org>; Thu, 11 Oct 2007 16:49:42 -0700 (PDT)
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: org-mode <emacs-orgmode@gnu.org>


The spate of design memos about GUIDs and scheduling leads me to ask
this :

is there any concept of "depends on" at all at the moment in org? I
don't see it if there is. e.g its quite possible to have a level one
task complete but a level 2 one incomplete.


** DONE PHP/HTTP authentication						   :WEB:
   SCHEDULED: <2007-10-13 Sat>
   - State "TODO"       [2007-10-12 Fri 01:30] \\
     get php /http authentication working
*** STARTED sub task
    SCHEDULED: <2007-10-12 Fri>
    - State "STARTED"    [2007-10-12 Fri 01:32] \\
      started
    - State "TODO"       [2007-10-12 Fri 01:31] \\
      blah