This is the mail archive of the
mailing list for the glibc project.
Re: Hash out a solution for ChangeLog/NEWS at the Cauldron?
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Carlos O'Donell <carlos at redhat dot com>
- Cc: Siddhesh Poyarekar <siddhesh at redhat dot com>, Martin Sebor <msebor at gmail dot com>, <libc-alpha at sourceware dot org>, <roland at hack dot frob dot com>
- Date: Wed, 5 Aug 2015 11:14:25 +0000
- Subject: Re: Hash out a solution for ChangeLog/NEWS at the Cauldron?
- Authentication-results: sourceware.org; auth=none
- References: <20150804173912 dot GC2504 at spoyarek dot pnq dot redhat dot com> <55C10308 dot 2050501 at gmail dot com> <55C14FD1 dot 8030105 at redhat dot com> <20150805003840 dot GG2504 at spoyarek dot pnq dot redhat dot com> <55C15F20 dot 4020004 at redhat dot com>
On Tue, 4 Aug 2015, Carlos O'Donell wrote:
> Ideally I'd like to see everything driven by git notes / git commit log
As I understand it notes aren't included by default in git clones / pull /
push. I don't think we should base things on anything git doesn't fetch
by default - just use version-controlled text files (whether such a file
listing fix-ups to the commit messages, or committing the generated
ChangeLog file when it's desired to fix something).
> * NEWS bug entry driven by "Resolves: #XXXX, #XXXX, #XXX" bug lines in
> commit log, with "Related: #XXXX" when not closing the bug but indicating
> you are fixing part of it.
Would those also generate the [BZ #N] annotations in the ChangeLog entry?
Note that for generating the NEWS entries you have to be able to allow for
a fix having been reverted, as well as for people getting the bug number
wrong or missing it in the first instance (and I suspect some of those
fix-ups are easier if the NEWS list of bugs comes from Bugzilla even if
the data in Bugzilla was first put there by a commit hook).
Joseph S. Myers