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:50:24 -0500	[thread overview]
Message-ID: <1136289024.9747.7.camel@vertigo.twi-31o2.org> (raw)
In-Reply-To: <1136237751.7702.30.camel@localhost>

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

On Tue, 2006-01-03 at 00:35 +0300, Peter Volkov (pva) wrote:
> On Вск, 2006-01-01 at 21:35 +0100, Francesco Riosa wrote:
> > We have currently 10371 ChangeLog files, > 25 MB totally .
> > 1365 == 13% with size >= 4096 B, 12 MB totally
> > 
> > rsync from "emerge --sync" has "--whole-file" between its options, that
> > mean transfer the whole file if changed.
> 
> > 2) "rotate" Changelogs, keeping only the last changes, until a size
> >    of 4000 or [choose a preferred size here] bytes.
> >    This would save only about 7Mb of data (max size < 4096).
> 
> ChangeLog is the only source of information on upgrade reasons and IMO
> users are interested only in recent information there. Another
> suggestion is to combine rotate like and exclude list solutions.
> 
> When ChangeLog size reaches above maximum allowed size echangelog should
> create ChangeLog.old file and copy tail of ChangeLog there, in order to
> keep ChangeLog size. Then using excludes list one may drop really old
> entries in ChangeLog.old, whereas keeping recent information in portage
> tree.

I could see this working well without removing the information from CVS
or the tree.  We would then add RSYNC_EXCLUDE on ChangeLog.old instead
of ChangeLog.  I wouldn't have a problem with this, and it would still
be benificial.  The only question left to be answered is how much space
would actually be saved to make this extra load on CVS worth it.

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

  reply	other threads:[~2006-01-03 12:11 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
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 [this message]
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=1136289024.9747.7.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