This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: small request regarding commits in binutils-gdb.git
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: Mike Frysinger <vapier at gentoo dot org>, fred dot cooke at gmail dot com, gdb-patches at sourceware dot org, binutils at sourceware dot org
- Date: Thu, 16 Jan 2014 06:17:02 +0400
- Subject: Re: small request regarding commits in binutils-gdb.git
- Authentication-results: sourceware.org; auth=none
- References: <20140115121251 dot GM4639 at adacore dot com> <201401151502 dot 09189 dot vapier at gentoo dot org> <83y52h2d5x dot fsf at gnu dot org> <201401151557 dot 48453 dot vapier at gentoo dot org> <83r4892brf dot fsf at gnu dot org>
> > not necessarily. there's two options:
> > - just use `git log --stat` and pipe it into a ChangeLog. this isn't a
> > "GNU ChangeLog", but it is a ChangeLog
>
> This is still a GNU project, isn't it? We still adhere to GNU coding
> standards, right? So I don't think we can avoid producing GNU-style
> ChangeLog files.
JIC we go further in that direction, the scripts I use to produce
the release make some commits, and one of the things they do is
extracting ChangeLog entries from commit text. It assumes the format
I have been using, which is
| path/to/ChangeLog:
|
| [ChangeLog text]
The code as is works well in the context of the controlled commits
the scripts are creating. They would probably need to be improved
for general usage, and the convention could also be adapted.
I would probably also add another "server"-side check to reject
improperly formatted commit logs prior to switching over to automatic
generation.
--
Joel