From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: hjl.tools@gmail.com, msnyder@vmware.com, mark.kettenis@xs4all.nl,
gdb-patches@sourceware.org
Subject: Re: [patch] more comment cleanups
Date: Mon, 03 Jan 2011 17:45:00 -0000 [thread overview]
Message-ID: <83pqsdop9i.fsf@gnu.org> (raw)
In-Reply-To: <20110103080610.GQ2396@adacore.com>
> Date: Mon, 3 Jan 2011 12:06:10 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: hjl.tools@gmail.com, msnyder@vmware.com, mark.kettenis@xs4all.nl,
> gdb-patches@sourceware.org
>
> That could be useful indeed. The solution we use at AdaCore is to write
> these entries only when checking in the CVS tree at sourceware. Internally,
> we no longer use the ChangeLog (the information is stored inside the
> revision log).
That's an okay solution for developers, but end users don't
necessarily access the repo, so the logs can still be useful for them.
(Of course, the logs could be generated from the repo when the release
is tarred, if the developers are disciplined enough to write log
messages that can serve as ChangeLog entries as well.)
next prev parent reply other threads:[~2011-01-03 17:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-31 23:26 Michael Snyder
[not found] ` <201012312312.oBVNC4fc013647@glazunov.sibelius.xs4all.nl>
[not found] ` <AANLkTimc4kNHOfO2B95cyKjN9SN1O_+LQ3O_4FpwZ3rR@mail.gmail.com>
2011-01-01 0:20 ` Michael Snyder
2011-01-01 9:11 ` Eli Zaretskii
2011-01-01 18:26 ` Michael Snyder
2011-01-03 4:43 ` Joel Brobecker
2011-01-03 5:06 ` H.J. Lu
2011-01-03 7:35 ` Joel Brobecker
2011-01-03 7:56 ` Eli Zaretskii
2011-01-03 8:06 ` Joel Brobecker
2011-01-03 17:45 ` Eli Zaretskii [this message]
2011-01-03 19:33 ` Doug Evans
2011-01-03 19:43 ` Eli Zaretskii
2011-01-03 8:05 ` Mark Kettenis
2011-01-03 20:35 ` Michael Snyder
2011-01-03 20:43 ` Eli Zaretskii
2011-01-03 13:00 ` Eli Zaretskii
2011-01-03 16:00 ` Joel Brobecker
2011-01-03 20:37 ` Michael Snyder
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=83pqsdop9i.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=mark.kettenis@xs4all.nl \
--cc=msnyder@vmware.com \
/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