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] | |
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 ... That particular script was just an example, so ideas for automating this are still welcome. Siddhesh
Attachment:
pgpx3IAgvvt6Z.pgp
Description: PGP signature
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |