On Thu, Apr 7, 2016 at 5:04 AM, John Regehr <reg...@cs.utah.edu> wrote:
> Argh, thanks, sorry for the noise! > > John > > > On 4/7/16 2:02 PM, Richard Hipp wrote: > >> On 4/7/16, John Regehr <reg...@cs.utah.edu> wrote: >> >>> What is the branch tag reported by fossil status? Perhaps the branch you >>>> were on got renamed? >>>> >>> >>> It says this: >>> >>> tags: pager-get-noinit >>> >>> whereas I had previously been on the trunk. Is that expected that I >>> will be silently moved between branches? >>> >>> >> Normally Fossil does not move between branches. Except, if you use >> the --latest option, it will move to the most latest descendent of the >> current check-out, regardless of the branch. So probably what >> happened is that you did "fossil up --latest" at a time when the >> pager-get-noinit branch was the latest descendent of the trunk >> check-in that you were previously on. But pager-get-noinit is >> currently a dead-end. (Maybe we'll merge it to trunk later, or maybe >> not - still undecided on that.) And so subsequent "fossil up >> --latest" commands do not move you off of that check-in because that >> check-in currently has no descendants. >> > >From a design-for-humans perspective I think fossil should stick to the branch *name*. The least surprising thing is to end up on the tip of the branch where you were working previously, not on the tip of some new branch. If I'm working on "trunk" and do a fossil update and end up on "some-debug-branch" I will be confused. The symbolic name is the critical data here IMHO. > >> If you want to move to the latest trunk check-in, then the command to >> use is "fossil update trunk". >> >> _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
