On Thu, 9 Feb 2012 08:19:36 -0000 "Eric" <[email protected]> wrote:
[...] > >> $ 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 [...] > > 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. The case presented by the original poster involved the pull step which appears to have suboptimal approach to reporting what we got from the remote repository. If you have autosync turned off (as I do everywhere, for instance) I just pull by hand, which changes nothing in this regard. That's why I referred to Git which, when you do "pulling" (it's called "fetching" in Git lingo) tells you "artifacts" for which branches it received, so you have an immediate idea about what has been changed on the remote. Hence my reference had nothing to do with Git's *workflow* in particular. > I wish people would stop expecting fossil to behave like git, if it > did you might as well use git. Please keep religious zealotry out of this list. Or at least try not to express it unless you are 100% sure you understood what the person to whose message you're responding to wanted to state. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
