Bernt Hansen <be...@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), Nick