From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [Council] ChangeLog generation within Gentoo
Date: Wed, 26 Oct 2011 17:56:36 -0600 [thread overview]
Message-ID: <20111026175636.79b66e26@gentoo.org> (raw)
In-Reply-To: 20111026193356.058efef7@neptune.home
[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]
On Wed, 26 Oct 2011 19:33:56 +0200
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).
>
> 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.
No, it's a pain in the ass to have to go pull up that info through cvs and
impossible when you're offline.
--
fonts, gcc-porting, it makes no sense how it makes no sense
toolchain, wxwidgets but i'll take it free anytime
@ gentoo.org EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-10-26 23:47 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
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 ` Ryan Hill [this message]
2011-10-27 7:34 ` 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=20111026175636.79b66e26@gentoo.org \
--to=dirtyepic@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