El mié, 26-10-2011 a las 19:33 +0200, Bruno escribió:
> On Wed, 26 October 2011 Fabian Groffen <grobian@gentoo.org> wrote:
> > However, this also allows to do all kinds of other actions to the
> > ChangeLog file, without actually adding an entry for the current change
> > being committed, as we've already seen in practice.
> > The Council would like to remind developers that it is still a
> > requirement that all actions are documented in the ChangeLog and that it
> > is hence the responsibility of the committing developer to make sure
> > this requirement is met.
> 
> Is there some guideline about old entries in the ChangeLog?
> 
> Over the past months ChangeLogs represent a big part of the tree, some
> of them being pretty big and going back many changes (hundreds of them)
> and years (even for actively maintained ebuilds).
> 
> In order to not bloat the tree I would like to see old entries purged
> when there are more than 25-50 of them, especially if they refer to
> ebuilds gone since more than 3-6 months.
> Someone in need for long gone ebuild would have to look at VCS anyhow, so
> looking at ChangeLog/history over there would seem logical.
> 
> On a compressed tree (squashfs) dropping all ChangeLogs reduces size from
> ~55MiB to around 35MiB which is quite a lot!
> 
> Bruno
> 
> 

Personally, I want to have full ChangeLog easily accessible, I remember
to need to look for really old entries when becoming a new maintainer
for an old package previously maintained by others.

What I don't know is the reasons for not compressing ChangeLogs by
default (well, I don't have a compressed tree, this probably won't be a
gain for people using it)