Peter Davis <peter@pdavis.cx> writes:
> Doesn't 'svn update' print out each file that it patches, adds, or deletes
> anyway? So really, considering how it behaves currently, it would look like:
>
> % svn update
> A ./foo
> M ./bar.txt
> Updated to revision 1788
> %
>
> So by your argument, 'svn update' should output nothing at all
> without a '-v'. Update is already a noisy command, so why not add a
> little more noise? Maybe noise is bad in Unix Philosophy, but on
> some level, none of this is noise -- it's useful information that
> the user *needs* to see with or without a '-v'. '-v' should be
> reserved for debugging-type information; useful information should
> be output regardless.
I hear ya. There is no way I'd ever run update without all its output
silenced. I use the output of update to know whether I need to re-run
gen-make.py (if new source files were added, or some deleted), whether
or not someone is working in code that's "close" to what I'm working
on (The "merged" status, or worse, a "conflict"). I mean, we're
talking about changing the contents of my disk without any
foreknowledge of what those contents will be -- by golly you better
believe I want to watch what's going on!
Besides, the "silence is golden" argument is bogus here unless it's a
call to change the UI for all of Subversion. If that's not the case,
I'd argue that consistency across the UI is much more useful
attribute, and as has been pointed out already, this change is
consistent with the output of other Subversion subcommands.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 26 17:16:37 2002