On Thu, February 9, 2012 7:47 am, Konstantin Khomoutov wrote: > On Thu, Feb 09, 2012 at 01:55:01AM +0100, frantisek holop wrote: > >> fossil always reports the latest artifact ID and commit message >> whenever doing 'fossil up', even though actually there was no new >> check-in. >> >> for example: >> >> $ fossil up >> Autosync: http://www.fossil-scm.org/ >> Bytes Cards Artifacts Deltas >> Sent: 177 2 0 0 >> Received: 2608 57 0 0 >> Total network traffic: 319 bytes sent, 1565 bytes received >> -------------- >> updated-to: 9b1d394a719f00f5a293612fe824e1a1fb1ed2e4 2012-02-08 >> 03:04:23 UTC >> tags: trunk >> comment: Update the version number to 1.22 and begin entering >> change log >> information for the next release. (user: drh) >> >> >> this confuses me sometimes thinking there was a new check-in :[ >> wouldn't it be more natural not to print anything if the local >> check-out is exactly as the remote one? and have this repeating >> output as part of the --verbose output? what do you think? > While I agree with you on this topic, a relatively easy way to spot that > there probably was a check-in is to look for non-zero count in the > "Deltas" column in the "Received" row. Non-zero "Artifacts" count means > that there were *some* changes, but they could relate to anything (bugs > filed, their state changed, wiki changes etc), and non-zero "Deltas" > indicates some files managed by fossil has been changed. > > Having said that, an output akin to Git's one would be way more helpful > in the general case: the list of branches which received updates with > symbolic indication about the kind of update occured.
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. Eric -- ms fnd in a lbry _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
