On Sun, May 01, 2011 at 12:00:17PM +0200, Fabian Groffen wrote:
> On 30-04-2011 11:46:37 +0300, Petteri Räty wrote:
> > http://devmanual.gentoo.org/ebuild-writing/misc-files/changelog/index.html
> > 
> > There doesn't seem to be a common opinion on what the policy for
> > ChangeLog entries is. See:
> > 
> > http://archives.gentoo.org/gentoo-dev/msg_f829da2375f1ceab766a800913cc4998.xml
> > 
> > I propose a simple new text: "Every commit should have an entry in
> > ChangeLog." If we eventually autogenerate them from git logs this would
> > happen any way (unless some kind of filtering system is in the middle)
> > so we could already start now. I think it's better to have more than
> > less information available to users.
> 
> Because everytime we need something more sophisticated people come up
> with the holy git grail, here is the script to generate a
> echangelog-style ChangeLog from CVS, right here, right now.
> 
> It's a naive implementation, but the output shows the differences
> between the committed log, and what would be generated from CVS.  (The
> usernames could be looked up easily, but I was too lazy to do that.)
> People can use this to judge if "autogeneration from VCS" is a good
> thing or not.
> 
> My conclusion is that you probably want to maintain the ChangeLog
> manually.
> 
> I also attached a sample of the script output for net-p2p/transmission
> for convenience.
> 
> 
> -- 
> Fabian Groffen
> Gentoo on a different level

Since most ( if not all ) of us use the same message on the Changelog
and on the commit log, it probably worth the effort of having the rsync
servers create the Changelogs before populate the portage tree. Having
the servers do that, will also allow us to provide cut down Changelogs
( lets say keep that last 10 entries ) so we can provide a more minimal
portage tree, size wise. A huge portage tree might not be a problem for
most of us but it sure is for embedded and all kind of similar systems.

Regards,
-- 
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2

Attachment: pgpAcl7C2U3Nr.pgp
Description: PGP signature

Reply via email to