Ludovic Brenta schrieb:
Ralf S. Engelschall [EMAIL PROTECTED] writes:
For me this looks like mtn db kill_rev_locally rev does not remove
_all_ related information of rev and that some remaining/dangling
information causes the subsequent commit to break. Hmm...
Unfortunately, I was not able
Thomas Keller [EMAIL PROTECTED] writes:
The problem is already fixed on mainline and goes into 0.37. The
roster which is attached to each revision is not removed, thus if you
try to commit the same revision again it cannot store the roster (which
has then the same revid) again. The fix now
I today had to use mtn db kill_rev_locally rev where rev was the
head of a branch. First, everything looked just fine. I freshly checked
out a new workspace (now based on the previous revision on the branch
which is now the new head), performed a mtn log to be sure that just
the previous head
Ralf S. Engelschall [EMAIL PROTECTED] writes:
I today had to use mtn db kill_rev_locally rev where rev was the
head of a branch. First, everything looked just fine. I freshly checked
out a new workspace (now based on the previous revision on the branch
which is now the new head), performed a
