Re: Markup problems when using references in source fragments

[Bernt Hansen <bernt@norang.ca>]

Nick Dokos <nicholas.dokos@hp.com> writes:

> Bernt Hansen <bernt@norang.ca> wrote:
>
>> Roland Kaufmann <rlndkfmn+orgmode@gmail.com> 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.

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.

>
> 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.

Regards,
Bernt