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] |
What I'm thinking of is a policy that'll allow us to auto-generate ChangeLog and NEWS from commit data so that whatever is posted on the list can be git-am'd directly and merged into master without rewriting the commit. This will allow for tighter integration with patchwork, to mark committed patches as closed automatically, leaving just superseded patches to clean up.
Would using Bugzilla to keep track of which release each bug was fixed in be a appealing solution? It would make it easier to find them and generate useful reports for each release. Such reports are often helpful when deciding which release to adopt. The NEWS file could also be generated from such a report just before each release. Martin
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |