Re: [fossil-users] When is 'tip' not 'trunk'

[jungle Boogie]

HI Clark,
On 9 June 2016 at 11:23, Clark Christensen  wrote:
>> 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.

1.35 is now released and you should use it:
https://www.fossil-scm.org/download.html

Updating software isn't necessarily always about things you can't live
without, but also bug fixes to both fossil and sqlite3. Since fossil
1.32 was released (2015-03-14), I count 19 sqlite3 releases:
http://sqlite.org/changes.html





-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
xmpp: jungle-boo...@jit.si
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] When is 'tip' not 'trunk'

[Warren Young]

On Jun 9, 2016, at 12:23 PM, Clark Christensen  wrote:
> 
> > Is there a good reason you can’t at least upgrade to the latest point 
> > release, 1.34?
> 
> I'm not sure what "the latest" offers that I can't live without.

The brief changelog is here:

  https://www.fossil-scm.org/index.html/doc/trunk/www/changes.wiki

Note that 1.35 changes appear there, but those are for the yet-to-be-released 
version.

> there's been a lot of discussion here about the behavior of 'mv' and ‘rm'

The specific changelog entry related to that discussion reads:

  • Add the --soft and --hard options to fossil rm and fossil mv. The default 
is still --soft, but that is now configurable at compile-time or by the 
mv-rm-files setting.

So, no change as far as you are concerned.

> Some want Fossil to modify the filesystem by default.  I do not.

I do, and for now, I must build Fossil with a configure script option that is 
disabled by default in order to make it do what I want.

> I can't remember what the outcome is WRT to Fossil's behavior here.

The last I heard, the behavior of that option will not change until Fossil 2.0, 
which as far as I can tell is still vaporware.

And even when/if that default does change, I expect there will be a way to 
return Fossil to its prior behavior.  In fact, this is signaled by the very 
name of the configure script option: --with-legacy-mv-rm.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] When is 'tip' not 'trunk'

[Clark Christensen]

> 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

Re: [fossil-users] When is 'tip' not 'trunk'

[Warren Young]

On Jun 7, 2016, at 3:24 PM, Clark Christensen  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