From: Nirbheek Chauhan <nirbheek@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] ChangeLog generation: Edit generated Changelogs
Date: Sat, 17 Sep 2011 14:37:17 +0530 [thread overview]
Message-ID: <CADqQcK7COZTp01zVdvX+aRPSPCqUw9FN81a+9DHcbu4UBwzBGA@mail.gmail.com> (raw)
In-Reply-To: <4E745B01.9040805@gentoo.org>
On Sat, Sep 17, 2011 at 2:02 PM, Markos Chandras <hwoarang@gentoo.org> wrote:
> In my opinion, we do not need to care about typos etc. We are human
> beings, so mistakes are part of our lives. Being able to fix
> post-generated changelogs will increase the size of $VCS since
> Changelogs need to be placed to $VCS for editing after generation and
> having a smart deduplication algorithm on the server side to filter
> duplicate messages. This is a bit stupid. If you make a mistake on
> your commit message, that's fine. Be careful next time.
>
I agree. Plus, if we use git-notes to *append* to ChangeLog entries
(in case you left out important information), we've covered all bases
as far as I'm concerned.
--
~Nirbheek Chauhan
Gentoo GNOME+Mozilla Team
next prev parent reply other threads:[~2011-09-17 9:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 14:08 [gentoo-project] ChangeLog generation: Edit generated Changelogs Markos Chandras
2011-09-16 21:32 ` "Paweł Hajdan, Jr."
2011-09-17 8:32 ` Markos Chandras
2011-09-17 9:07 ` Nirbheek Chauhan [this message]
2011-09-17 14:01 ` Rich Freeman
2011-09-19 13:26 ` Fabian Groffen
2011-09-19 13:44 ` Markos Chandras
2011-09-19 14:27 ` Fabian Groffen
2011-09-19 16:28 ` Markos Chandras
2011-09-19 16:51 ` Fabian Groffen
2011-09-19 16:58 ` Markos Chandras
2011-09-19 17:09 ` Fabian Groffen
2011-09-19 17:21 ` Markos Chandras
2011-09-19 17:53 ` Fabian Groffen
2011-09-19 21:39 ` Donnie Berkholz
2011-09-19 21:46 ` Michał Górny
2011-09-20 6:57 ` Fabian Groffen
2011-09-28 17:37 ` Fabian Groffen
2011-09-28 18:24 ` Mr. Aaron W. Swenson
2011-09-29 17:04 ` Markos Chandras
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=CADqQcK7COZTp01zVdvX+aRPSPCqUw9FN81a+9DHcbu4UBwzBGA@mail.gmail.com \
--to=nirbheek@gentoo.org \
--cc=gentoo-project@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