Le 2012-02-09 à 05:04, frantisek holop <min...@obiit.org> a écrit :
> hmm, on Thu, Feb 09, 2012 at 08:19:36AM -0000, Eric said that >> fossil update is concerned only with the branch you have in your checkout >> directory. If autosync is on it does a pull first, but that's a separate >> operation, and it os concerned only with artifacts in the repository and >> knows nothing about branches. I wish people would stop expecting fossil to >> behave like git, if it did you might as well use git. > > 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. -- Martin G. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
