patchwork.sourceware.org is live!
Ondřej Bílka
neleai@seznam.cz
Wed Jun 4 10:28:00 GMT 2014
On Fri, May 30, 2014 at 08:30:29AM +0530, Siddhesh Poyarekar wrote:
> On Thu, May 29, 2014 at 09:56:55PM -0400, Samuel Bronson wrote:
> > Are there any objections to the new state?
>
> None so far. I have added it to patchwork now. I have not yet made
> 'Accepted' an 'Action Required' state because that will clutter the
> view; I'll do it when I get explicit blessings from more maintainers.
>
> > > That should be set automatically. I use a following script to detect
> > > commited patches.
> >
> > If there are no objections, I guess the script will need to be changed
> > to put patches in the "Committed" state instead of the "Accepted" state?
> >
> > However, really I'd prefer if it could give some indication as to
> > *which* commit(s) the patch was committed as, and it doesn't look like
> > this is viable with the current approach, since you seem to just test if
> > each patch can be applied backwards to HEAD.
> >
> > Oh, but now I notice that that *particular* script is glibc-only anyway,
> > so maybe I don't really care that much ...
>
Its pretty general, you can use it for any project that uses git. A
more important part is running automated checks with it.
More information about the Libc-alpha
mailing list