[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Command-line verbosity

From: Steve Kemp <skx_at_tardis.ed.ac.uk>
Date: 2000-10-23 22:42:10 CEST

On Mon, 23 Oct 2000, Jim Blandy wrote:
> When I do an update, CVS spits out a line for every file it changes.
> If there are a lot of changes (which happens often), and there is a
> conflict anywhere but in the last screenful of output, and I don't
> *watch* the CVS command running, I end up trying to compile '>>>>>>'
> somewhere.

  I've had the same problem, using WinCVS.
> Anytime I have to carefully grub through pages of output, most of
> which is just "business as usual", I think the interface is borken.
> Here are two possible solutions that occurred to me:

> - (Radical.) CVS shouldn't print out the lines of the files it
> modifies unless you ask it to. Honestly, do you really read all of
> them and examine the changes? It should only report things that
> need attention, like conflicts.
  Surely thats the sort of thing that a "--quiet" flag should be

> - (Less Radical.) After telling you about each file it touched, CVS
> should print a blank line, and then reiterate the things which
> require attention.

  If by that you mean that every other line of output is blank, then
 it seems to be producing masses of output, which would be a) time
 consuming, and b) exaserbating the problem. (Consider the case where
 the error was eight lines from the bottom of the console; now its
 16 lines from the bottom, and potentially of the screen).

  How about option number three:

  - After processing all the files, (perhaps printing errors as it
 goes), the errors could all be duplicated, eg:


-- Errors --
Failed to merge foo.cpp


# There is no Steve...
Received on Sat Oct 21 14:36:12 2006

This is an archived mail posted to the Subversion Dev mailing list.