[Sugar-devel] Managing own patches on patchwork (was: Re: [PATCH] Announce file transfer capabilities #1603)

Tomeu Vizoso tomeu at sugarlabs.org
Fri Sep 24 12:13:25 EDT 2010

On Tue, Sep 21, 2010 at 02:14, James Cameron <quozl at laptop.org> wrote:
> On Mon, Sep 20, 2010 at 10:57:49PM +0200, Sascha Silbe wrote:
>> BTW, it would be nice if patch submitters would update the state of their
>> own patches on patchwork [1], especially if they get superseded by newer
>> patch versions or accepted into mainline.
>> This is entirely optional, but helps reducing the load on maintainers.
> Neat.  Didn't know I could do that.
> Advice for others: get an account if you don't have one yet, log in,
> look in the patches list, identify those that are superceded, click on
> them, update the state and optionally click on archived, then update.

Just did it for the patches I submitted, if others could do the same
would be great.



> --
> James Cameron
> http://quozl.linux.org.au/
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel

More information about the Sugar-devel mailing list