Trimming dead branches

Alban Hertroys alban.hertroys at apollovredestein.com
Wed Feb 11 09:17:40 UTC 2015


We're currently having some issues with failing commits due to file 
locking issues and those failed commits are causing dead branches in our 
repo. In TortoiseHg's workbench we can see several new branches with 
commit messages equal to the final successful commit attempt.

If we "backout" such dead branches, does that modify our repo in any way 
other than removing those dead branches?

For the record, it appears that those file locking issues are caused by a 
combination of:
* the 3 of us using the same repo on a remote Windows share,
* which is also used by the (web-based) product we develop in; WebFOCUS, 
which appears to keep locks on certain files (namely procedures) longer 
than necessary,
* in combination with us using the keywords extension, because our users 
like to be able to see whether the production version of their reports is 
up-to-date with the latest developments that they cleared for production 
use.

That's a bit of a tricky setup we realise, but we haven't found a way 
around that actually works. Separate development environments didn't work 
out, for example.

Regards,

Alban Hertroys.
(apologies for the silly footer that comes next, I have no control over 
that)


alban.hertroys at apollovredestein.com
T: 




 	Apollo Vredestein B.V. - P.O. Box 27 - 7500 AA  Enschede - The Netherlands - 
Chamber of Commerce number 34223268 - http://www.apollovredestein.com	 

The information contained in this e-mail is intended solely for the use of the 
individual or entity to whom it is addressed and others authorized to receive 
it. You are hereby notified that any disclosure, copying, distribution or 
action in relation to the contents of this information is strictly prohibited. 
If you are not the intended recipient, please delete this message and any 
attachments and advise the sender by return e-mail. The confidentiality of this 
message is not warranted. Apollo Vredestein B.V. rules out any and every 
liability resulting from this or any other electronic transmission.
 



More information about the Mercurial mailing list