From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Re: [gentoo-dev] ChangeLog generation - pros and cons (council discussion request)
Date: Tue, 9 Aug 2011 13:15:01 -0500 [thread overview]
Message-ID: <20110809181501.GH25611@comet.mayo.edu> (raw)
In-Reply-To: <20110809174211.GD24618@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1320 bytes --]
On 19:42 Tue 09 Aug , Fabian Groffen wrote:
> On 09-08-2011 12:32:57 -0500, Donnie Berkholz wrote:
> > > > Yeah, that's already on my draft agenda [1]. =) But we should still have
> > > > a small set of options to choose from if we do vote to automate, so we
> > > > don't sit around for another month or discuss it aimlessly for hours.
> > > > Being prepared is what I'm hoping we can do here.
> > >
> > > Ok, then I suggest simply adding ", don't bother about changes between
> > > CVS log and ChangeLog" to both of your options.
> >
> > I guess I don't understand something here. If we aren't retroactively
> > changing existing ChangeLogs, and we're autogenerating things in the
> > future, where would these changes come from?
>
> so you want to retain all existing ChangeLogs?
Seems like a better idea to me, although it's not originally mine. Old
commit messages weren't written with the knowledge or intent that anyone
would be reading them, except maybe a dev or two, so we might lose a lot
of information.
If/when we switch to git, we might want to reconsider that, since all
the handwritten messages will be old, largely irrelevant history by
then.
--
Thanks,
Donnie
Donnie Berkholz
Council Member / Sr. Developer
Gentoo Linux
Blog: http://dberkholz.com
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-08-09 18:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110602091338.GL14065@gentoo.org>
2011-08-01 20:16 ` [gentoo-project] Re: [gentoo-dev] ChangeLog generation - pros and cons (council discussion request) Fabian Groffen
2011-08-03 17:43 ` Donnie Berkholz
2011-08-03 17:56 ` Fabian Groffen
2011-08-03 18:09 ` Donnie Berkholz
2011-08-03 18:33 ` Fabian Groffen
2011-08-09 17:32 ` Donnie Berkholz
2011-08-09 17:42 ` Fabian Groffen
2011-08-09 18:15 ` Donnie Berkholz [this message]
2011-08-09 18:22 ` Fabian Groffen
2011-08-09 20:20 ` Donnie Berkholz
2011-08-09 20:26 ` Fabian Groffen
2011-08-09 18:34 ` Samuli Suominen
2011-08-03 18:16 ` Markos Chandras
2011-08-03 18:30 ` Fabian Groffen
2011-08-03 18:39 ` Markos Chandras
2011-08-03 18:43 ` Fabian Groffen
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=20110809181501.GH25611@comet.mayo.edu \
--to=dberkholz@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