From: <dsmich@adelphia.net>
To: hanwen@xs4all.nl
Cc: guile-devel@gnu.org
Subject: Re: RFD: please drop ChangeLog updates
Date: Thu, 28 Aug 2008 12:30:08 -0400 [thread overview]
Message-ID: <21676570.1219941008413.JavaMail.root@web20> (raw)
---- Han-Wen Nienhuys <hanwen@xs4all.nl> wrote:
> 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.
Guile is distributed as a tarball, not a git repo. Does it make sense to create the ChangeLog from the git log at make dist time?
-Dale
next reply other threads:[~2008-08-28 16:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 16:30 dsmich [this message]
2008-08-29 2:47 ` RFD: please drop ChangeLog updates 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
-- strict thread matches above, loose matches on Subject: below --
2008-08-28 14:40 Han-Wen Nienhuys
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=21676570.1219941008413.JavaMail.root@web20 \
--to=dsmich@adelphia.net \
--cc=guile-devel@gnu.org \
--cc=hanwen@xs4all.nl \
/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).