This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Patchwork for libc-alpha


Hi Jeremy,

First I want to thank you to setting this up for GLIBC. However, you probably didn't
follow the glibc patchwork discussion. To summarize it for you, Siddhesh already setup
up an experimental one:

http://patchwork.siddhesh.in/project/glibc/list/

His idea is to keep it for a month or so and then moving it to sourceware.org. I think
his idea and also Carlos' one is to keep all the GLIBC development tools (bugzilla
and patchwork) on the same place.

Siddhesh and Carlos, did you summarize your plan correctly?


On 14-03-2014 02:57, Jeremy Kerr wrote:
> Hi all,
>
> Khem Raj has asked me to set up a patchwork instance for libc-alpha;
> I've just done so, patches will be listed at:
>
>   http://patchwork.ozlabs.org/project/glibc/list/
>
> And general patchwork project info at:
>
>   http://patchwork.ozlabs.org/project/glibc/list/
>
> [https will work too]
>
> Khem tells me that this is more experimental at this stage, so there are
> no maintainers defined for the project. Once you decide on
> maintainer(s), please let me know the patchwork usernames and I'll set
> the appropriate permissions.
>
> Some background for those not familiar with patchwork: patchwork is
> subscribed to libc-alpha, and catches anything that it parses as a
> patch. This will be added to the project patch list, in a 'New' state.
> Follow-up comments on patches are also included in the page for the patch.
>
> Maintainers can update the state of a patch, typically to 'Accepted' or
> 'Rejected'.
>
> This allows contributors to see what's happened to their patch, and
> gives maintainers a list of pending contributions.
>
> There's a command-line client for patchwork, called pwclient. This can
> be used to list, search and download patches, and maintainers can update
> patch states too. Details are here:
>
>  http://patchwork.ozlabs.org/help/pwclient/
>
> One handy snippet is my patchwork 'catch-up' script. Given two revisions
> (rev1 and rev2) in git, it will iterate over the changes to find
> matching patchwork patches, and update their status:
>
>   # Patchwork “catchup” script
>   git rev-list rev1..rev2 |
>   while read commit
>   do
>       hash=$(git show $commit | pwparser --hash)
>       pwclient update -s Accepted -c $commit -h $hash
>   done
>
> (you'll need a copy of patchwork's parser for that, grab it with:
>
>  wget -O pwparser
> http://git.ozlabs.org/?p=patchwork;a=blob_plain;f=apps/patchwork/parser.py;hb=HEAD
>
> Happy patchworking,
>
>
> Jeremy
>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]