From: Brian Harring <ferringb@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Devmanual text on ChangeLogs
Date: Sun, 1 May 2011 13:43:25 -0700 [thread overview]
Message-ID: <20110501204325.GF23166@hrair> (raw)
In-Reply-To: <4DBD22A7.3080500@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1528 bytes --]
On Sun, May 01, 2011 at 12:06:47PM +0300, Samuli Suominen wrote:
> ... the time alone if you have to stop on each package to wait for
> echangelog to get done just doubles the amount of time you have to put
> into committing them. That's just not worth the effort.
This argument sucks; if the tool is problematic... fix the tool.
Simple example, why is is it interactive?
Add a -m <message> option to it; no longer have to watch it, just fire
the command in a term (or in screen) w/ the message given to it
already.
Beyond that... I suspect *everyone* would appreciate optimization done
to echangelog. From a quick look... seems like it's cvs status, than
a cvs diff. Trying to collapse that into a single op, falling back to
status might not be a bad thing (or parallelizing the requests so the
slowness of cvs doesn't cause sequentially stack up).
Either way.. fix the tool, rather than just doing the wrong thing.
> So not only they are rather useless, and information you can easily get
> from sources.gentoo.org, they take your time as well.
I think the dial up users would have a real issue with your "easily
get from sources.g.o" statement- same for users like myself when I'm
in public transit/flying/working somewhere than work and at home (I
actually do use those logs when I'm checking depgraph/pcheck issues).
Either way, fix the tool, or prove that the tool can't go any faster,
and *then* it's a potential discussion. Right now it really isn't,
imo.
~brian
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-05-01 20:44 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-30 8:46 [gentoo-dev] Devmanual text on ChangeLogs Petteri Räty
2011-04-30 9:02 ` Samuli Suominen
2011-04-30 12:12 ` Peter Volkov
2011-05-02 2:23 ` Jeroen Roovers
2011-04-30 13:42 ` Markos Chandras
2011-04-30 14:24 ` Brian Harring
2011-04-30 18:16 ` Alex Alexander
2011-04-30 20:39 ` Panagiotis Christopoulos
2011-05-01 9:06 ` Samuli Suominen
2011-05-01 10:09 ` [gentoo-dev] git? [was: Re: Devmanual text on ChangeLogs] Eray Aslan
2011-05-01 10:54 ` [gentoo-dev] git? Panagiotis Christopoulos
2011-05-01 11:25 ` Andreas K. Huettel
2011-05-01 18:05 ` [gentoo-dev] git? [was: Re: Devmanual text on ChangeLogs] Maciej Mrozowski
2011-05-01 10:34 ` [gentoo-dev] Devmanual text on ChangeLogs Fabian Groffen
2011-05-01 10:44 ` Panagiotis Christopoulos
2011-05-01 11:26 ` Peter Volkov
2011-05-01 11:26 ` Andreas K. Huettel
2011-05-01 20:43 ` Brian Harring [this message]
2011-05-02 2:43 ` Jeroen Roovers
2011-04-30 9:07 ` Ulrich Mueller
2011-04-30 11:21 ` Panagiotis Christopoulos
2011-05-02 2:52 ` Jeroen Roovers
2011-04-30 12:28 ` [gentoo-dev] " Diego Elio Pettenò
2011-04-30 13:05 ` Panagiotis Christopoulos
2011-04-30 13:44 ` "Paweł Hajdan, Jr."
2011-04-30 14:00 ` Rich Freeman
2011-04-30 9:57 ` [gentoo-dev] " Pacho Ramos
2011-05-01 10:00 ` Fabian Groffen
2011-05-01 14:55 ` [gentoo-dev] " Duncan
2011-05-01 15:08 ` Fabian Groffen
2011-05-01 21:08 ` [gentoo-dev] " Markos Chandras
2011-05-01 22:33 ` Brian Harring
2011-05-01 22:49 ` Markos Chandras
2011-05-01 23:23 ` [gentoo-dev] " Duncan
2011-05-01 23:31 ` Brian Harring
2011-05-01 23:43 ` Rich Freeman
2011-05-02 0:13 ` Markos Chandras
2011-05-02 1:15 ` Duncan
2011-05-02 6:48 ` Fabian Groffen
2011-05-02 0:16 ` Markos Chandras
2011-05-02 21:10 ` Arfrever Frehtes Taifersar Arahesis
2011-05-01 23:11 ` Duncan
2011-05-02 0:04 ` [gentoo-dev] " Ulrich Mueller
2011-05-02 0:21 ` Markos Chandras
2011-05-02 1:20 ` Nirbheek Chauhan
2011-05-02 1:24 ` Robin H. Johnson
2011-05-02 1:37 ` Nirbheek Chauhan
2011-05-02 5:17 ` Ulrich Mueller
2011-05-02 6:51 ` Fabian Groffen
2011-05-02 21:24 ` Gilles Dartiguelongue
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=20110501204325.GF23166@hrair \
--to=ferringb@gmail.com \
--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