mercuria destroys everyone's work
Franklin M. Siler
fsiler at gmail.com
Thu Jan 14 10:53:30 UTC 2016
On Jan 14, 2016, at 0135, FLORENT Philippe <Philippe.FLORENT at edenred.com> wrote:
> After a few months of usage, we thought we tamed the beast
> We thought installing our reps on a windows share had solved many issues
> Well, no we still loose code and hours of work
> countless hours repairing the new code that mercurial discarded in favour of older code without asking
> Countless hours repairing/recreating our repositories when they just crash for no reason, us unable to push our new commits
> We did not change the way we work with it, and after a month of “””correct””” behavior, the whole thing once again get completely messed up
> I officialy renounce, this package is an unstable and clearly not suited for a prod environment
I’d like to apologize for your difficulties, and for some of the replies on this list. It sounds as though you no longer want to use Mercurial, and that’s understandable. Are you planning a migration away from Mercurial, or would you like help? If so, can you explain what you are trying to do and what your workflow looks like?
Cheers,
Frank Siler
Siler Industrial Analytics
314.799.9405
More information about the Mercurial
mailing list