From: Han-Wen Nienhuys <hanwen@xs4all.nl>
To: guile-devel@gnu.org
Subject: Re: git and changelogs
Date: Sat, 17 May 2008 17:53:23 -0300 [thread overview]
Message-ID: <g0ngl4$cav$1@ger.gmane.org> (raw)
In-Reply-To: <87bq3f1br2.fsf@gnu.org>
Ludovic Courtès escreveu:
>> Now that we've switched to git, hows about moving our changelogs to
>> ChangeLog.old, and just using commit logs? We can still generate
>> changelogs on release, if that's a desire.
>
> I'd be tempted to do that, but among the many GNU projects that switched
> to Git, apparently none of them did away with ChangeLogs, and I would
> understand reluctance to remove them.
LilyPond was the first project to switch to Git, and the ChangeLog was one
of the first things that we junked.
* It's a nuisance, because it always conflicts on merges.
* After you've used
git log -Ssuspect_text -p branch --
the ChangeLog looks like a joke.
* We did have some autogenerated changelogs for a while, but I have
never seen any evidence that they were used.
--
Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen
next prev parent reply other threads:[~2008-05-17 20:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 15:38 git and changelogs Andy Wingo
2008-05-09 20:08 ` Ludovic Courtès
2008-05-17 20:53 ` Han-Wen Nienhuys [this message]
2008-05-09 22:41 ` Neil Jerram
2008-05-11 3:09 ` Ludovic Courtès
2008-05-12 19:10 ` Andy Wingo
2008-05-12 20:12 ` Neil Jerram
2008-05-12 21:35 ` Andy Wingo
2008-05-22 21:02 ` Thien-Thi Nguyen
2008-07-11 22:22 ` Neil Jerram
2008-07-15 18:08 ` Ludovic Courtès
2008-07-15 18:28 ` Neil Jerram
2008-07-15 18:54 ` Ludovic Courtès
2008-07-16 21:51 ` Ludovic Courtès
2008-07-17 21:24 ` Neil Jerram
2008-07-17 21:29 ` Neil Jerram
2008-07-18 13:05 ` Ludovic Courtès
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='g0ngl4$cav$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).