From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [Council] ChangeLog generation within Gentoo
Date: Wed, 26 Oct 2011 14:02:12 -0400 [thread overview]
Message-ID: <CAGfcS_nqk0CS87eMQzXE+s4N566AmUqfA=_h+MBUjM21O0zWQg@mail.gmail.com> (raw)
In-Reply-To: <CAATnKFCtKg=Fd=ofF88n2CL3-yOVvROzhDc6qqdg13A3ws2CEQ@mail.gmail.com>
On Wed, Oct 26, 2011 at 1:56 PM, Kent Fredric <kentfredric@gmail.com> wrote:
> On 27 October 2011 06:33, Bruno <bonbons67@internet.lu> wrote:
>>
>> 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).
>>
>
> A lot of the older changelog entries also tend to be less normal, and some
> long changelogs are so a-typical its virtually impossible to parse them with
> machine code.
Well, if the desire to trim changelogs is generally agreed upon we
could always just count the lines and post a top-100 list or something
and let package maintainers go in and truncate things as seems bet to
them, with the guideline to keep the file intact up to a year before
the last commit. Eventually the files will be cleaned up.
Rich
next prev parent reply other threads:[~2011-10-26 18:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 17:02 [gentoo-dev] [Council] ChangeLog generation within Gentoo Fabian Groffen
2011-10-26 17:33 ` Bruno
2011-10-26 17:56 ` Kent Fredric
2011-10-26 18:02 ` Rich Freeman [this message]
2011-10-26 21:00 ` Fabian Groffen
2011-10-27 3:28 ` [gentoo-dev] " Duncan
2011-10-27 7:05 ` Fabian Groffen
2011-10-26 18:07 ` [gentoo-dev] " Pacho Ramos
2011-10-26 19:24 ` Bruno
2011-10-26 23:56 ` [gentoo-dev] " Ryan Hill
2011-10-27 7:34 ` [gentoo-dev] " Michael Haubenwallner
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='CAGfcS_nqk0CS87eMQzXE+s4N566AmUqfA=_h+MBUjM21O0zWQg@mail.gmail.com' \
--to=rich0@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