- Mar 12, 2008
-
-
Thomas Arendsen Hein authored
-
- Feb 21, 2008
-
-
Gilles Moris authored
Currently, backout is creating a backout revision as a child node of the backed out node and will leave you at this new head. This has several drawbacks: * this changes the current head * when there is a long history between the backed out node and the current head, this will generate a huge number of diffs that are scary at first sight, and not very natural to review before commit. The change consists to switch back to the original node as soon as the backout node (which becomes the new tip) has been created. Then the --merge option can just merge this new tip in the current node. * the current head/node is not changed from the user's point of view * even without using the --merge option, the backout revision is still easy to locate, as this is the tip * the merge is much more intuitive as diffs of the merge is right you are looking to backout
-
- Feb 17, 2008
-
-
Thomas Arendsen Hein authored
commit (aborts _after_ typing in a commit message) backout (aborted after the initial revert) tag (edited .hgtags and couldn't commit) import (patch applied, then commit fails) qnew (aborts on bad dates, but writes any valid date into the # Date header) qrefresh (like qnew) sign (like tag) fetch (merge, merge, merge, merge, abort)
-
- Jul 22, 2007
-
-
Matt Mackall authored
We use weak references (ugh) to avoid having to manually delete transaction references out of each call frame when an exception occurs.
-
- Dec 06, 2006
-
-
Matt Mackall authored
-
- Oct 03, 2006
-
-
Jose M. Prieto authored
-
Jose M. Prieto authored
-
Jose M. Prieto authored
-
- Aug 21, 2006
-
-
Matt Mackall authored
Move default message to commands.py Pass node in binary for consistency Remove default arguments Fix up tests
-
- Jun 30, 2006
-
-
Benoit Boissinot authored
-
Jose M. Prieto authored
-