hmm, on Thu, Feb 09, 2012 at 05:58:47AM -0500, Martin Gagnon said that
> > i have never used git.  i would simply prefer fossil to report nothing
> > if there is nothing to report...
> > 
> > $ fossil up
> > $
> > 
> > come to think of it, as a developer i am not really interested in
> > fossil's traffic statistics either, it is more distracting than useful
> > and would expect such extra information under --verbose.
> > perhaps my minimalism is too maximal :]
> > 
> 
> That's might be a good output when autosync is off. But if autosync is ON, we 
> should see something related to the sync step. 
> 
> Indeed, the sync step (or pull/push) might be slimmed a bit too. I would 
> suggest only a progress or a counter refreshing a single line (using "\r"), 
> so we can see if there's activity. If the sync step have no output, one might 
> confuse very long sync with network timeout and an impatient will <CTRL-C> 
> too early.

by all means, if there is some activity (pulling and/or pushing),
report it.  but the case i was referring to is when i am pushing
nothing, and pulling nothing.  as fossil returns to shell right
away, i think the outcome is clear.  regarding the network
timeouts, no program reports them until they time out :]

-f
-- 
if you live long enough, it will kill you...
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to