From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jambunathan K Subject: Re: org-capture (lost PATCH?) Date: Tue, 28 Sep 2010 10:09:42 +0530 Message-ID: <81d3ryv5v5.fsf@gmail.com> References: <81hbha3arh.fsf@gmail.com> <87ocbi4n41.fsf@fastmail.fm> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from [140.186.70.92] (port=58270 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P0Rz4-0005ow-43 for emacs-orgmode@gnu.org; Tue, 28 Sep 2010 00:40:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1P0Rz2-0005Hh-PS for emacs-orgmode@gnu.org; Tue, 28 Sep 2010 00:40:05 -0400 Received: from mail-iw0-f169.google.com ([209.85.214.169]:43218) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1P0Rz2-0005HV-C7 for emacs-orgmode@gnu.org; Tue, 28 Sep 2010 00:40:04 -0400 Received: by iwn33 with SMTP id 33so8803500iwn.0 for ; Mon, 27 Sep 2010 21:39:59 -0700 (PDT) In-Reply-To: <87ocbi4n41.fsf@fastmail.fm> (Matt Lundin's message of "Mon, 27 Sep 2010 22:29:18 -0400") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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: Matt Lundin Cc: emacs-orgmode@gnu.org, Carsten Dominik Matt >> I had proposed a patch to org-capture in this thread. >> >> http://lists.gnu.org/archive/html/emacs-orgmode/2010-08/msg01152.html >> >> The patch has neither been rejected nor accepted. I am a bit concerned >> that it might have been lost. > > It's currently on patchwork with the status of "deferred": > > http://patchwork.newartisans.com/patch/246/ Thanks. Reassuring to know that this is still under the radar. >From the patchwork server side, two things could be considered: 1. Enhance the web interface[1] to show *all* *not DONE* items. - http://patchwork.newartisans.com/project/org-mode/list/ 2. Generate an automated reply to a submitter of the patch giving him an URL to the patch. This will enable under the hood access to the patch state. Either or both of 1 and 2 would avoid anxiety on contributor's side particularly the newer ones. Thanks, Jambunathan K.