public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] ChangeLogs and rsync time
Date: Tue, 03 Jan 2006 06:47:27 -0500	[thread overview]
Message-ID: <1136288847.9747.4.camel@vertigo.twi-31o2.org> (raw)
In-Reply-To: <43B97CE7.1070101@gentoo.org>

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

On Mon, 2006-01-02 at 13:20 -0600, Lance Albertson wrote:
> > 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.

So you have now taken what was described as an automatic solution to
reduce size into a manual process, reducing usability of the ChangeLog
and increasing workload for every ebuild developer.

I'm sorry, but I still think the idea of simply RSYNC_EXCLUDEing the
ChangeLog by default would be a much better solution.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2006-01-03 12:08 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
2006-01-02 23:08                   ` Paweł Madej
2006-01-03  5:28                   ` Donnie Berkholz
2006-01-03 11:47                   ` Chris Gianelloni [this message]
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=1136288847.9747.4.camel@vertigo.twi-31o2.org \
    --to=wolf31o2@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