From: Nirbheek Chauhan <nirbheek@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [git migration] The problem of ChangeLog generation
Date: Tue, 13 Apr 2010 17:18:04 +0530 [thread overview]
Message-ID: <u2z8b4c83ad1004130448xca6953a3t5c5146f10e38e2ad@mail.gmail.com> (raw)
In-Reply-To: <1271157930.11850.977.camel@tablet>
On Tue, Apr 13, 2010 at 4:55 PM, Peter Volkov <pva@gentoo.org> wrote:
> В Втр, 06/04/2010 в 07:43 +0530, Nirbheek Chauhan пишет:
>> * It makes zero sense to manually manage ChangeLogs in git[1]
>
> Once I had stupid cut&paste mistake and entered wrong credits in
> ChangeLog. I don't see how to resolve this issue in case ChangeLog's
> will be generated from git log and until somebody suggests how to edit
> ChangeLogs generated from git I think have to keep ChangeLogs in
> gentoo-x86.
>
I didn't know that editing existing ChangeLog entries manually was an
accepted practice with CVS. Even if it was to correct typos or
something else.
The traditional ChangeLog that is currently employed in gentoo-x86
(and in other projects) is simply an ugly hack to cheaply distribute
commit messages to users in an offline manner.
Think of it like this: if you make a typo in a commit message, or
forget to add something; you can't change it after you've published
the commit (cvs/svn commit or git push) to the world. Since ChangeLogs
are offline commit messages; you shouldn't edit them either; only
(app|pre)pend to them.
Also, with git, you usually review and double-check your commits and
amend/rebase before pushing, so such mistakes can be corrected then.
And now that we have the ability to cheaply generate ChangeLogs from
the commit messages, there is no reason to keep this ugly hack around.
--
~Nirbheek Chauhan
Gentoo GNOME+Mozilla Team
next prev parent reply other threads:[~2010-04-13 11:48 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 2:13 [gentoo-dev] [git migration] The problem of ChangeLog generation Nirbheek Chauhan
2010-04-06 6:41 ` Fabian Groffen
2010-04-06 7:01 ` Nirbheek Chauhan
2010-04-06 11:40 ` Fabian Groffen
2010-04-07 9:58 ` Angelo Arrifano
2010-04-07 10:03 ` Ciaran McCreesh
2010-04-07 14:36 ` Richard Freeman
2010-06-21 19:34 ` [gentoo-dev] " Christian Faulhammer
2010-04-06 7:28 ` [gentoo-dev] [git migration] Proposition for tags supported by git hooks Maciej Mrozowski
2010-04-06 8:00 ` Nirbheek Chauhan
2010-04-06 13:06 ` [gentoo-dev] [git migration] The problem of ChangeLog generation Richard Freeman
2010-04-06 22:21 ` Robin H. Johnson
2010-04-07 10:05 ` Angelo Arrifano
2010-04-07 6:25 ` Hans de Graaff
2010-04-07 7:55 ` Dirkjan Ochtman
2010-04-07 16:54 ` Markos Chandras
2010-04-07 18:41 ` Nirbheek Chauhan
2010-04-07 21:54 ` Markos Chandras
2010-04-13 11:25 ` Peter Volkov
2010-04-13 11:44 ` Angelo Arrifano
2010-04-13 11:48 ` Nirbheek Chauhan [this message]
2010-04-13 13:19 ` Ulrich Mueller
2010-04-13 13:35 ` Nirbheek Chauhan
2010-04-13 16:12 ` Matti Bickel
2010-04-13 16:22 ` Angelo Arrifano
2010-04-13 16:23 ` Alec Warner
2010-04-13 16:33 ` Matti Bickel
2010-04-14 1:47 ` Richard Freeman
2010-04-14 6:39 ` Nirbheek Chauhan
2010-04-14 9:08 ` Matti Bickel
2010-04-13 16:47 ` Peter Volkov
2010-05-02 15:13 ` Jim Ramsay
2010-06-24 18:59 ` Luca Barbato
2010-06-24 20:43 ` Olivier Crête
2010-06-25 8:45 ` Peter Volkov
2010-06-25 8:49 ` Arun Raghavan
2010-06-25 9:00 ` Peter Volkov
2010-06-26 5:55 ` Olivier Crête
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=u2z8b4c83ad1004130448xca6953a3t5c5146f10e38e2ad@mail.gmail.com \
--to=nirbheek@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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