From: Lance Albertson <ramereth@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] ChangeLogs and rsync time
Date: Mon, 02 Jan 2006 13:20:07 -0600 [thread overview]
Message-ID: <43B97CE7.1070101@gentoo.org> (raw)
In-Reply-To: <1136227249.7131.1.camel@vertigo.twi-31o2.org>
[-- Attachment #1: Type: text/plain, Size: 2218 bytes --]
Chris Gianelloni wrote:
> On Mon, 2006-01-02 at 11:25 -0600, Lance Albertson wrote:
>
>>>I'm also for telling the users to rsync exclude the ChangeLogs if they
>>>don't want them instead of getting rid of them or crippling them.
>>
>>I don't think that's really a solution. That's just a way to minimize
>>what they get. If you really want to look at a solution, you should
>>reduce whats actually in the changelog. All the changelogs are in CVS,
>>and if someone wanted to go look back at any changes, they can either
>>look at viewcvs or (hopefully soon), grab it via anoncvs. I bet you >80%
>>of things in the changelogs are for things that are in the attic. I say
>>we need a way to either have echangelog (or another script) to clean out
>>changelog entries for things that are in the attic (and make sense to
>>take out). Maybe another option would be to remove any 'version bump'
>>type entries that are old as well.
>
>
> OK. I keep seeing this argument about ChangeLog stuff for ebuilds in
> the Attic and I just think people might not be thinking it totally
> trough. For example, I made changes to the vmware-workstation ebuilds
> to force group membership a while back because of a security bug.
> However, there's been another security bug since, so those changes were
> made on ebuilds now in Attic, but the change is still valid in the
> current ebuilds.
>
> I don't see a problem with removing version bump and stabilization
> messages, but everything else should stay in the ChangeLog for as long
> as the package is still around.
See the part that I said "make sense to take out". What you described is
a perfect example of something that needs to stay. All I'm getting at is
that minor things that the package maintainer thinks isn't important to
keep in the active changelog, should be able to be removed. I'm not
implying to blindly remove changelog entries solely based on the fact
that those ebuilds are in the attic. Common sense would play here.
--
Lance Albertson <ramereth@gentoo.org>
Gentoo Infrastructure | Operations Manager
---
GPG Public Key: <http://www.ramereth.net/lance.asc>
Key fingerprint: 0423 92F3 544A 1282 5AB1 4D07 416F A15D 27F4 B742
ramereth/irc.freenode.net
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-01-02 20:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-01 20:35 [gentoo-dev] ChangeLogs and rsync time Francesco Riosa
2006-01-01 21:48 ` Grobian
2006-01-01 22:43 ` [gentoo-dev] " Duncan
2006-01-02 9:26 ` [gentoo-dev] " Francesco Riosa
2006-01-04 9:22 ` Brian Harring
2006-01-01 22:55 ` Ciaran McCreesh
2006-01-01 23:50 ` Andrej Kacian
2006-01-02 9:37 ` Francesco Riosa
2006-01-02 10:44 ` Paweł Madej
2006-01-02 15:00 ` Matti Bickel
2006-01-02 16:37 ` Francesco Riosa
2006-01-02 16:45 ` Matti Bickel
2006-01-02 16:47 ` Henrik Brix Andersen
2006-01-02 17:25 ` Lance Albertson
2006-01-02 18:40 ` Chris Gianelloni
2006-01-02 19:20 ` Lance Albertson [this message]
2006-01-02 23:08 ` Paweł Madej
2006-01-03 5:28 ` Donnie Berkholz
2006-01-03 11:47 ` Chris Gianelloni
2006-01-03 12:18 ` Re[2]: " Jakub Moc
2006-01-03 14:29 ` Paweł Madej
2006-01-03 14:35 ` Mike Frysinger
2006-01-02 23:47 ` Francesco Riosa
2006-01-01 22:59 ` Andrej Kacian
2006-01-02 9:12 ` Francesco Riosa
2006-01-02 21:35 ` Peter Volkov (pva)
2006-01-03 11:50 ` Chris Gianelloni
2006-01-03 17:56 ` Francesco Riosa
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=43B97CE7.1070101@gentoo.org \
--to=ramereth@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