emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: Bernt Hansen <bernt@norang.ca>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: Markup problems when using references in source fragments
Date: Thu, 12 May 2011 09:48:42 -0400	[thread overview]
Message-ID: <8484.1305208122@alphaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Bernt Hansen <bernt@norang.ca> of "Thu, 12 May 2011 08:43:43 EDT." <8739kknl6o.fsf@norang.ca>

Bernt Hansen <bernt@norang.ca> 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),


  reply	other threads:[~2011-05-12 13:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-11 19:41 Markup problems when using references in source fragments (was: Markup on same line as text) Roland Kaufmann
2011-05-11 19:51 ` Markup problems when using references in source fragments Bernt Hansen
2011-05-11 20:06   ` Roland Kaufmann
2011-05-11 20:21     ` Bernt Hansen
2011-05-12  6:59       ` Nick Dokos
2011-05-12 10:56         ` Giovanni Ridolfi
2011-05-12 12:43         ` Bernt Hansen
2011-05-12 13:48           ` Nick Dokos [this message]
2011-05-25  7:41 ` Markup problems when using references in source fragments (was: Markup on same line as text) Carsten Dominik
2011-05-25 10:31   ` Carsten Dominik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8484.1305208122@alphaville.dokosmarshall.org \
    --to=nicholas.dokos@hp.com \
    --cc=bernt@norang.ca \
    --cc=emacs-orgmode@gnu.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).