From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: Markup problems when using references in source fragments Date: Thu, 12 May 2011 09:48:42 -0400 Message-ID: <8484.1305208122@alphaville.dokosmarshall.org> References: <4DCAE660.2020008@gmail.com> <87boz9nhhr.fsf@norang.ca> <4DCAEC36.1080909@gmail.com> <877h9xng2k.fsf@norang.ca> <5257.1305183584@alphaville.dokosmarshall.org> <8739kknl6o.fsf@norang.ca> Reply-To: nicholas.dokos@hp.com Return-path: Received: from eggs.gnu.org ([140.186.70.92]:47520) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QKWGN-0005PM-Fl for emacs-orgmode@gnu.org; Thu, 12 May 2011 09:49:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QKWGJ-0001dv-Dg for emacs-orgmode@gnu.org; Thu, 12 May 2011 09:49:11 -0400 Received: from vms173003pub.verizon.net ([206.46.173.3]:43823) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QKWGJ-0001do-25 for emacs-orgmode@gnu.org; Thu, 12 May 2011 09:49:07 -0400 Received: from alphaville.dokosmarshall.org ([unknown] [173.76.32.106]) by vms173003.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0LL300KFH516Q3D0@vms173003.mailsrvcs.net> for emacs-orgmode@gnu.org; Thu, 12 May 2011 08:48:55 -0500 (CDT) In-reply-to: Message from Bernt Hansen of "Thu, 12 May 2011 08:43:43 EDT." <8739kknl6o.fsf@norang.ca> 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: Bernt Hansen Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org Bernt Hansen wrote: > >> I think you can create an account on the patchwork server and then > >> invalidate your own patches. > >> > > > > If this is possible, can somebody please give details? There is at least > > one post of mine that ended up as /patch/797/ that should certainly be > > invalidated, since it quotes the patch from an older commit. > > Hi Nick, > > I think you just register an account on the patchwork server that > matches your patch email address, then when you login and select your > patch you get an option to invalidate it. > Indeed - I missed the login/register/about links. > > > > And while we are at it: is there any way to mark a post that contains a > > patch as "not intended for the patchwork server"? One would have to > > remember to do that, so it's not foolproof, but it might help avoid > > piling irrelevant stuff on patchwork. > > I'm not aware of a way to do this currently - maybe just put [RFC] or > something in the subject line of the patch so it's obviously not > complete and ready for inclusion? - then you can just remove the patch > from the patchwork server after posting it. I don't know if the > patchwork server has any rules for skipping patches. > OK - actually, thinking about it some more, it might make more sense to implement the opposite: add the patch if the subject line includes a cookie (e.g. [PATCH]), the rationale being that somebody who is consciously submitting a patch for inclusion will be in a better position to remember to do that. In any case, not my decision. Thanks (and thanks to Giovanni too for the email suggestion), Nick