On Fri, 2016-11-04 at 16:58 -0700, Martin von Zweigbergk via Mercurial-devel wrote: > # HG changeset patch > # User Martin von Zweigbergk <martinv...@google.com> > # Date 1478303512 25200 > # Fri Nov 04 16:51:52 2016 -0700 > # Node ID bb80851fe9a6e14263f0076074108556377141f9 > # Parent cb2bac3253fbd52894ffcb4719a148fe6a3da38b > fold: disallow multiple revisions without --exact > > It's very easy to think that "hg fold 4::6" will fold exactly those > revisions. In reality, it will fold those *and* any revisions between > them and the working copy. It seems very likely that users who pass > more than one revision wants to fold exactly those revisions, so let's > abort and hint that they may be looking for --exact.
There was some kind of explicit reason for why originally Pierre-Yves convinced me that the current behaviour was correct. Something about how `hg fold 'draft()'` would be a common thing. I can't remember the justification anymore, something about how it's impossible to predict in advance if a revset is a single or multiple commits. I think I agree with everyone that --exact should probably just become the default again as it once was. No more `hg fold .^`, you must now do `hg fold '. + .^'` like before. Everyone seems to really want --exact and gets surprised by the magic of trying to include "." in the folded set. _______________________________________________ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
