> When the most recently modified branch is trunk, then tip and trunk
> happen to be the same. Otherwise, they will point to different
> checkins.Understood. Thanks for the quick answer.
> Is there a good reason you can’t at least upgrade to the latest point
> release, 1.34?
Valid point. I'm not sure what "the latest" offers that I can't live without.
Plus, there's been a lot of discussion here about the behavior of 'mv' and
'rm'. Some want Fossil to modify the filesystem by default. I do not. I
can't remember what the outcome is WRT to Fossil's behavior here. So I'm lazy
about adopting 'the latest' without spending the time to understand what
changed. Especially when what I have continues to work reliably.
-Clark
From: Warren Young <w...@etr-usa.com>
To: Fossil SCM user's discussion <fossil-users@lists.fossil-scm.org>
Sent: Wednesday, June 8, 2016 3:41 AM
Subject: Re: [fossil-users] When is 'tip' not 'trunk'
On Jun 7, 2016, at 3:24 PM, Clark Christensen <cdcmi...@yahoo.com> wrote:
>
> Hit an unexpected thing today cloning a just-committed repo to a new computer.
What do you get on the “tags:” line of the “fossil status” command’s output
when run from the directory where you made that commit?
If it is anything other than “trunk,” your results are exactly what you should
expect.
> But I don't understand why trunk and tip are not the same.
If they were the same, we wouldn’t need two different terms, now would we?
trunk is the name of a special branch that exists from the creation of the
repository. If you make no branches, you will only have the trunk.
tip is the most recent checkin on the most recently modified branch.
When the most recently modified branch is trunk, then tip and trunk happen to
be the same. Otherwise, they will point to different checkins.
> Both clients (committer and cloner) have fossil version 1.32 [6c40678e91]
> 2015-03-14 13:20:34 UTC on Windows 7x64
That’s getting a bit old now. Is there a good reason you can’t at least
upgrade to the latest point release, 1.34?
I often use old binary versions of Fossil myself…just long enough to clone the
fossil-scm.org repo and build the current trunk version.
_______________________________________________
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
