From: Han-Wen Nienhuys <hanwen@xs4all.nl>
To: guile-devel@gnu.org
Subject: RFD: please drop ChangeLog updates
Date: Thu, 28 Aug 2008 11:40:16 -0300 [thread overview]
Message-ID: <g96des$uv6$1@ger.gmane.org> (raw)
Reasons:
* Much more detailed and inherently correct information can be gotten from
git log -- libguile/
git log -- test-suite/
etc.
* The ChangeLog duplicates the git log information if done correctly. Hence
it requires double work for the committer.
* Since updates to the ChangeLog always happen at the top, they virtually
always conflict on pulls and cherry-picks. This makes it impossible to
use the power of git. For example, rebase is the standard git approach
to creating linear history of changes. This is apparently something
the GUILE devs think is important, but the changes to ChangeLog ensure
that every cherry pick will need manual conflict resolution.
--
Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen
next reply other threads:[~2008-08-28 14:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 14:40 Han-Wen Nienhuys [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-28 16:30 RFD: please drop ChangeLog updates dsmich
2008-08-29 2:47 ` Han-Wen Nienhuys
2008-08-29 9:46 ` Sergey Poznyakoff
2008-08-29 19:56 ` Ludovic Courtès
2008-08-29 23:47 ` Han-Wen Nienhuys
2008-08-30 18:40 ` Ludovic Courtès
2008-08-30 19:11 ` Han-Wen Nienhuys
2008-08-30 19:31 ` Ludovic Courtès
2008-08-30 21:11 ` Neil Jerram
2008-08-31 10:30 ` Ludovic Courtès
2008-08-30 0:32 ` Andy Wingo
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='g96des$uv6$1@ger.gmane.org' \
--to=hanwen@xs4all.nl \
--cc=guile-devel@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).