From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: RFD: please drop ChangeLog updates
Date: Sun, 31 Aug 2008 12:30:12 +0200 [thread overview]
Message-ID: <87fxolcw97.fsf@gnu.org> (raw)
In-Reply-To: 49dd78620808301411j21012fcet5785d0bbccb6a339@mail.gmail.com
Hello,
"Neil Jerram" <neiljerram@googlemail.com> writes:
> Actually, perhaps it would be nicer to put both those notes in a top
> level file called "ChangeLog", rather than in HACKING.
Yes, that's the most obvious place to put information about ChangeLogs.
Other ChangeLogs can be renamed as you suggested.
> Finally, I'm assuming that there would be no change to the quality or
> style of the information that we used to put in ChangeLogs; the only
> difference is that the same information will now be in the commit
> message. Is that what everyone else is assuming too?
Yes, that's my assumption, too, which is why I was looking for an Emacs
mode to simplify the task.
As far as releases are concerned, we can surely use one of these scripts
to generate a top-level ChangeLog. It doesn't seem too complicated and
may be handy for users who don't want to browse the Git repository.
Thanks,
Ludo'.
next prev parent reply other threads:[~2008-08-31 10:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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=87fxolcw97.fsf@gnu.org \
--to=ludo@gnu.org \
--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).