public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matti Bickel <kabel@cat0.de>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] ChangeLogs and rsync time
Date: Mon, 2 Jan 2006 17:45:26 +0100	[thread overview]
Message-ID: <20060102164526.GB6819@pluto.atHome> (raw)
In-Reply-To: <43B956DC.9060402@gentoo.org>

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

Francesco Riosa <vivo@gentoo.org> wrote:
> Matti Bickel wrote:
> > Pawe?? Madej <linux@quanteam.info> wrote:
> >> As a common user with ADSL 256kbps all additional data downloaded via
> >> rsync causes longer wait for syncing. If I want to see a changelog i
> >> go to packages.gentoo.org and read it. As i got Gentoo for about 10
> >> months I don't remember if I read Changelog via bash.
> > 
> > I strongly disagree. Reading changelogs on the web means browsing for
> > them. This is much slower for me than a 'less
> > /usr/portage/foo/bar/Changelog'.
> > 
> > I rather go with ciaranm and tell users to use rsync_exclude if they
> > don't want changelogs. Taking away choice without an option is a bad
> > thing (tm).
> 
> A (rethoric) question:
> Do you read every time the whole ChangeLog ?
> If not, generally, how much of it ?

About 20%. I don't care about changelogs most of the time because
diffing the ebuilds is easier and you get more info.
However if there's a bug or some major upgrade, i tend to kind of read
the thing. For bug# and stuff.

Personally it's also interesting who commited a fix.

Regards,
Matti
-- 

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-01-02 16:48 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 [this message]
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
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=20060102164526.GB6819@pluto.atHome \
    --to=kabel@cat0.de \
    --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