From: Alan Modra <amodra@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Mike Frysinger <vapier@gentoo.org>,
fred.cooke@gmail.com, gdb-patches@sourceware.org,
brobecker@adacore.com, binutils@sourceware.org
Subject: Re: small request regarding commits in binutils-gdb.git
Date: Thu, 16 Jan 2014 02:11:00 -0000 [thread overview]
Message-ID: <20140116021051.GC5390@bubble.grove.modra.org> (raw)
In-Reply-To: <83r4892brf.fsf@gnu.org>
On Wed, Jan 15, 2014 at 11:09:08PM +0200, Eli Zaretskii wrote:
> 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.
People have been putting the changelog entry in the git log. If that
continues, it ought to be easy to generate a GNU ChangeLog by "git log
| awk". I don't see any need for a ChangeLog in the source
repository if we can generate one to be distributed along with the
sources.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2014-01-16 2:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 12:12 Joel Brobecker
2014-01-15 15:28 ` Mike Frysinger
2014-01-15 15:51 ` Tom Tromey
2014-01-15 16:04 ` Eli Zaretskii
2014-01-15 16:25 ` Joel Brobecker
2014-01-15 16:57 ` Eli Zaretskii
2014-01-15 17:12 ` Mike Frysinger
2014-01-15 19:48 ` Fred Cooke
2014-01-15 20:02 ` Mike Frysinger
2014-01-15 20:38 ` Eli Zaretskii
2014-01-15 20:57 ` Mike Frysinger
2014-01-15 21:09 ` Eli Zaretskii
2014-01-16 2:11 ` Alan Modra [this message]
2014-01-16 2:17 ` Joel Brobecker
2014-01-16 1:41 ` Fred Cooke
2014-01-16 2:41 ` Mike Frysinger
2014-01-15 16:50 ` Pedro Alves
2014-01-15 17:03 ` Tom Tromey
2014-01-15 18:07 ` Gary Benson
2014-01-16 11:41 ` Jose E. Marchesi
2014-01-15 19:31 ` Cary Coutant
2014-01-15 19:45 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140116021051.GC5390@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=fred.cooke@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=vapier@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox