With all this talk about how to keep draft work out of the repo when done with 
it, I started playing with the various methods mentioned.

I noticed the following, and I would like to know if this expected behavior or 
some bug.
Regardless, it is disturbing to lose trunk (or other branch) commits without 
any warning, especially when that branch is not explicitly mentioned in the 
PURGE command.

Here’s the (Win7) commands to reproduce:
-------------------------------------------
f new xxx.fossil
f o xxx.fossil
f com --force --branch base -m "Empty branch"
f up trunk
dir > a
f add a
f com -m "Added file"
dir > a
f com --branch other -m "Revised file"
dir > a
f com -m "Second revision of file"
f up trunk
f me other
f com -m "Merged other"
f ui
rem Next command gives error: cannot purge the current checkout
f pur other
rem Try again from 3rd independent branch
f up base
f pur other
f ui
-------------------------------------------

At the two UI commands my output is this (before and after):


BEFORE PURGE OTHER


AFTER PURGE OTHER

If there were more commits in trunk after 5963, all of the them would be gone!  
I understand PURGE will kill all descendants of the given tag(s) but ‘trunk’ is 
not a sole descendant of ‘other’, as it also inherits ‘trunk’ so I would expect 
the propagation of the purge to stop right before the merge (i.e., after 
purging 0081).

The same procedure with --private, does not have this problem, and works as (I) 
expected.

I assume this is the reason ‘cannot purge the current checkout’ error is issued 
when trying the purge from within trunk.  But trying from a 3rd branch, no 
warning about destroying trunk.

Regardless, I would expect PURGE to only affect checkins 579b and 0081, and 
nothing more.  This is what happens if the OTHER branch is declared –private
(f com --branch other -m "Revised file" –private)

So, why this difference.  Is this for a reason or a bug?

Thanks.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to