From: Bernt Hansen <email@example.com>
Cc: Roland Kaufmann <firstname.lastname@example.org>, email@example.com
Subject: Re: Markup problems when using references in source fragments
Date: Thu, 12 May 2011 08:43:43 -0400 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Nick Dokos's message of "Thu, 12 May 2011 02:59:44 -0400")
Nick Dokos <firstname.lastname@example.org> writes:
> Bernt Hansen <email@example.com> wrote:
>> Roland Kaufmann <firstname.lastname@example.org> writes:
>> > On 2011-05-11 21:51, Bernt Hansen wrote:
>> >> Both the new and old patch are on the patchwork server waiting to be
>> >> addressed.
>> > Oops, sorry my bad. I didn't realize that!
>> > However, only the discussion from the first thread:
>> > <http://patchwork.newartisans.com/patch/525/>
>> > is revelant. The patch which is listed there should *not* be
>> > applied. A second and corrected patch was attached in the last
>> > message, but it seems to not have been picked up by the framework.
>> > How do I replace the patch above with the code from:
>> > <http://patchwork.newartisans.com/patch/802/>
>> > --
>> > Roland.
>> 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.
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.
> 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.
next prev parent reply other threads:[~2011-05-12 12:43 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 [this message]
2011-05-12 13:48 ` Nick Dokos
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
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 \
* 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).