[PATCH v4] rollback: add a config knob for entirely disabling the command
Kevin Bullock
kbullock+mercurial at ringworld.org
Mon May 9 14:44:07 UTC 2016
On May 8, 2016, at 18:02, Pierre-Yves David <pierre-yves.david at ens-lyon.org> wrote:
> While keeping in mind than "deprecated" does not mean "flagged for removal" it might still be a good idea to eventually disable 'hg rollback'. As Greg pointed, it can lead to unrecoverable data loss and as Sean pointed out, we did it in the past for small thing like 'hg strip -b'. An extra element to take in account is that the actual result of 'hg rollback' have been shifting a lot in the past years as more and more things are using transaction. So scripting using 'hg rollback' might have already broke multiple times (especially if they do a lot of local operation, pull should be fine, push is not).
>
> I'm not saying we should do it, but I think there might be some room to think about it if someone is willing to make a full analysis.
I'm open to being convinced (and obviously mine is not the final say on the matter).
pacem in terris / мир / शान्ति / سَلاَم / 平和
Kevin R. Bullock
More information about the Mercurial-devel
mailing list