From: Nick Roberts <nickrob@snap.net.nz>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Daniel Jacobowitz <drow@false.org>,
pedro@codesourcery.com, gdb-patches@sourceware.org
Subject: ChangeLog entries [was Re: [non-stop] 01/10 Add "executing" property]
Date: Mon, 16 Jun 2008 06:45:00 -0000 [thread overview]
Message-ID: <18517.57202.90761.74048@kahikatea.snap.net.nz> (raw)
In-Reply-To: <uzlpmjcfu.fsf@gnu.org>
> > Do you really think it's useful? We've never asked to
> > do this (see the cvs log of Makefile.in for plenty of examples), and I
> > would resist; changelogs already take a long time to write.
>
> It's common practice in GNU projects. I'm quite shocked to learn that
> some of us resist it. Yes, our log entries are already quite sloppy
> and unhelpful, but there are limits.
I find the ChangeLog useful as a starting point to understand when and why
changes to individual files were made. It's probably hard to prescribe
_exactly_ what should go in but I've never looked at a ChangeLog to understand
when and why a dependency was added to a Makefile. So I'm inclined to agree
with Daniel. It's pretty straightforward to determine whether a dependency is
needed or not - no need to go trawling through the CVS history.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2008-06-16 3:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-15 21:04 [non-stop] 01/10 Add "executing" property Pedro Alves
2008-06-15 22:18 ` Eli Zaretskii
2008-06-16 1:42 ` Daniel Jacobowitz
2008-06-16 3:23 ` Eli Zaretskii
2008-06-16 6:45 ` Nick Roberts [this message]
2008-06-16 7:22 ` Vladimir Prus
2008-06-17 0:40 ` Eli Zaretskii
2008-06-17 17:10 ` Vladimir Prus
2008-06-17 20:38 ` Eli Zaretskii
2008-06-23 17:27 ` Tom Tromey
2008-06-17 16:14 ` Joel Brobecker
2008-06-17 18:24 ` Eli Zaretskii
2008-06-17 18:32 ` Joel Brobecker
2008-06-18 0:22 ` Eli Zaretskii
2008-06-17 18:34 ` Pedro Alves
2008-06-17 20:58 ` Eli Zaretskii
2008-06-23 1:13 ` Daniel Jacobowitz
2008-06-23 11:54 ` Vladimir Prus
2008-06-23 14:41 ` Pedro Alves
2008-06-23 18:22 ` Eli Zaretskii
2008-06-23 18:25 ` Vladimir Prus
2008-06-23 19:52 ` Pedro Alves
2008-06-24 1:13 ` Eli Zaretskii
2008-06-23 18:14 ` Eli Zaretskii
2008-07-02 3:29 ` Pedro Alves
2008-06-25 19:02 ` Vladimir Prus
2008-06-25 19:13 ` Pedro Alves
2008-06-25 19:22 ` Daniel Jacobowitz
2008-06-26 13:37 ` Vladimir Prus
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=18517.57202.90761.74048@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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