- Jan 09, 2016
-
-
Yuya Nishihara authored
cmdutil.command wasn't a member of the registrar framework only for a historical reason. Let's make that happen. This patch keeps cmdutil.command as an alias for extension compatibility.
-
- Dec 07, 2015
-
-
Gregory Szorc authored
-
- Oct 08, 2015
-
-
Pierre-Yves David authored
The home of 'Abort' is 'error' not 'util' however, a lot of code seems to be confused about that and gives all the credit to 'util' instead of the hardworking 'error'. In a spirit of equity, we break the cycle of injustice and give back to 'error' the respect it deserves. And screw that 'util' poser. For great justice.
-
- Nov 22, 2014
-
-
Siddharth Agarwal authored
This test extension manages the opts it cares about on its own anyway.
-
- May 05, 2014
-
-
Gregory Szorc authored
-
- Nov 25, 2012
-
-
Matt Mackall authored
-
- Jun 18, 2011
-
-
Matt Mackall authored
The most appropriate context is not always clearly defined. The obvious cases: For working directory commands, we use None For commands (eg annotate) with single revs, we use that revision The less obvious cases: For commands (eg status, diff) with a pair of revs, we use the second revision For commands that take a range (like log), we use None
-
- May 13, 2011
-
-
Matt Mackall authored
-
Matt Mackall authored
This allows users at levels below the command layer to avoid import loops.
-
- Jan 01, 2010
-
-
Patrick Mezard authored
In worst case, generating diff in upgrade mode can be two times more expensive than generating it in git mode directly: we may have to regenerate the whole diff again whenever a git feature is detected. Also, the first diff attempt is completely buffered instead of being streamed. That said, even without having profiled it yet, I am convinced we can fast-path the upgrade mode if necessary were it to be used in regular diff commands, and not only in mq where avoiding data loss is worth the price.
-