Re: Philip, is issue #1556 easy for you?

Philip Martin <philip@codematters.co.uk> writes:
> That will mean a additional line in the output, and the way I use
> Subversion it will mean that I get a "please wait" message immediately
> before the command exits. Is this new output really necessary? It's
> not really an improvement in every case.

True. It would be a (very) mild annoyance to those who are not having
a problem.

But to those who *are* having a problem, it's a big difference -- to
them, it looks like Subversion is stuck, and this would clue them in
that it's not. After a few minutes (a realistic amount of time if you
have a big enough tree combined with a slow enough disk) of mysterious
inaction, anyone would be tempted to hit ^C.

I'm certainly not wedded to the idea of an extra line of output, if we
can think of a better solution to this problem.

The message doesn't have to actually say "please wait", of course,
that was just my example. It could simply say

   Releasing locks...
   Updated to revision 8888.

The pause, if there is one, would go between those two lines. At
least that would give people a language to express what's happening.
"Subversion seems to spend a long time releasing locks when I update."
"Oh, how big is your tree?" "Pretty big." "Okay, then it's normal."

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Nov 11 05:38:10 2003