El 30/9/2007, a las 15:49, Pierre Habouzit escribió:
On Sun, Sep 30, 2007 at 12:45:34PM +0000, Wincent Colaiuta wrote:
I think that most people just want to know, "Did it work or not?"
and so
when the commands chatter too much they go into filter mode, don't
really
read the output, let alone try to understand it, and just skim it.
Ideally Git would be much less "chattery" in general when things
work,
and only be more verbose when things go wrong; of course, finding
that
balance point is where the art lies.
That's true for git merge that is fast. But people also want to know
the command is not stuck in an infinite loop, and for that progress
bars
or little \|/- animation.
Yes, I agree. I probably should have said that they either want to
know "*Did* it work?" for near-instant operations (most Git
operations, hopefully), and "*Is* it working?" for long-running ones
(network ops, for example) and in those cases you're right that a
progress bar would be a nice enhancement.
Cheers,
Wincent
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
