public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
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 11:25:16 -0600	[thread overview]
Message-ID: <43B961FC.10609@gentoo.org> (raw)
In-Reply-To: <20060102164729.GA31727@osgiliath.brixandersen.dk>

[-- Attachment #1: Type: text/plain, Size: 1735 bytes --]

Henrik Brix Andersen wrote:
> On Mon, Jan 02, 2006 at 05:37:48PM +0100, Francesco Riosa wrote:
> 
>>Do you read every time the whole ChangeLog ?
>>
>>If not, generally, how much of it ?
> 
> 
> I often find myself grepping through the entire ChangeLog too see when
> and who introduced a particular change in an ebuild - but I normally
> do this in my CVS check-out.
> 
> 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.

I just don't see the point of keeping changelog entries for stuff that
isn't even viewable in the tree anymore. We have CVS, the record will be
there, lets use it. We can't cater to every user out there, but come up
with a solid solution that makes sense and still gives them some form of
ability to look back.

-- 
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 --]

  reply	other threads:[~2006-01-02 17:28 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 [this message]
2006-01-02 18:40               ` Chris Gianelloni
2006-01-02 19:20                 ` Lance Albertson
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=43B961FC.10609@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