From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Hendy Subject: Re: Item task_id not being used in taskjuggler export Date: Mon, 1 Apr 2013 22:27:01 -0500 Message-ID: References: <87eheutjpz.fsf@gmail.com> <876206th04.fsf@gmail.com> <87wqsmryt0.fsf@gmail.com> <87sj3arxk0.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([208.118.235.92]:47324) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UMrsG-0001SS-N0 for emacs-orgmode@gnu.org; Mon, 01 Apr 2013 23:27:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UMrsE-0006lZ-Nj for emacs-orgmode@gnu.org; Mon, 01 Apr 2013 23:27:04 -0400 Received: from mail-lb0-f171.google.com ([209.85.217.171]:39951) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UMrsE-0006lU-Fy for emacs-orgmode@gnu.org; Mon, 01 Apr 2013 23:27:02 -0400 Received: by mail-lb0-f171.google.com with SMTP id v10so50602lbd.2 for ; Mon, 01 Apr 2013 20:27:01 -0700 (PDT) In-Reply-To: <87sj3arxk0.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nicolas Goaziou Cc: emacs-orgmode On Mon, Apr 1, 2013 at 12:05 PM, Nicolas Goaziou wrote: > John Hendy writes: > >> Process: >> - Save your patch to ~/Downloads/patch.patch >> - cd ~/.elisp/org.git >> - git branch tj-test >> - git checkout tj-test >> - patch -p1 < ~/Downloads/patch.patch >> - make clean && make >> - start fresh Emacs session > > Dismiss the patch. I pushed the changes into master. You should update > Org, reload it, and try again. Sorry -- I thought you were still describing the behavior of the patch you sent. Posted in the other thread with the results, which are that: - ID is correctly assigned now - Depends resolve as long as there is only one global instance of that specific task_id - If you depend on a non-globally-unique task_id (e.g. there is an M.T1 and also a T.T1, and you use =:depends: T1=), that task will end up depending on both of them. Best regards, John > > > Regards, > > -- > Nicolas Goaziou