| 1 |
On Sun, May 01, 2011 at 12:06:47PM +0300, Samuli Suominen wrote: |
| 2 |
> ... the time alone if you have to stop on each package to wait for |
| 3 |
> echangelog to get done just doubles the amount of time you have to put |
| 4 |
> into committing them. That's just not worth the effort. |
| 5 |
|
| 6 |
This argument sucks; if the tool is problematic... fix the tool. |
| 7 |
Simple example, why is is it interactive? |
| 8 |
|
| 9 |
Add a -m <message> option to it; no longer have to watch it, just fire |
| 10 |
the command in a term (or in screen) w/ the message given to it |
| 11 |
already. |
| 12 |
|
| 13 |
Beyond that... I suspect *everyone* would appreciate optimization done |
| 14 |
to echangelog. From a quick look... seems like it's cvs status, than |
| 15 |
a cvs diff. Trying to collapse that into a single op, falling back to |
| 16 |
status might not be a bad thing (or parallelizing the requests so the |
| 17 |
slowness of cvs doesn't cause sequentially stack up). |
| 18 |
|
| 19 |
Either way.. fix the tool, rather than just doing the wrong thing. |
| 20 |
|
| 21 |
|
| 22 |
> So not only they are rather useless, and information you can easily get |
| 23 |
> from sources.gentoo.org, they take your time as well. |
| 24 |
|
| 25 |
I think the dial up users would have a real issue with your "easily |
| 26 |
get from sources.g.o" statement- same for users like myself when I'm |
| 27 |
in public transit/flying/working somewhere than work and at home (I |
| 28 |
actually do use those logs when I'm checking depgraph/pcheck issues). |
| 29 |
|
| 30 |
Either way, fix the tool, or prove that the tool can't go any faster, |
| 31 |
and *then* it's a potential discussion. Right now it really isn't, |
| 32 |
imo. |
| 33 |
~brian |
Archives