On Tue, Mar 30, 2010 at 07:18, Junio C Hamano <gitster@xxxxxxxxx> wrote: > Nicolas Pitre <nico@xxxxxxxxxxx> writes: > >> Personally I like your suggestion above. A clone is not something you >> perform repeatedly, and it is the first thing that random people told to Well, I have git clone in my top-20 used commands. I'm reasonably sure it is used many times in a row too. >> use Git to grab a piece of code will do. Better give them some comfort >> by telling them what is happening. > > Here is what such a change may look like. I'll leave adjusting > documentation (namely, tutorials) and perhaps tests as an exercise to the > readers ;-) There still is no way to make things quiet by default. And at least for me the annoyance was when using it in command line, interactively. So yes, it makes it possible to make clone quieter, but I wont use it, because I have to either make an alias for git (and that on every system I might come upon), or type in "-q" every time, at which case I can also live with a little more output. But even if it is of no immediate use to me personall, I still like the patch: now I can make some scripts quieter (with less risk of removing something interesting by piping everything to /dev/null). -- 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