- Jun 10, 2010
-
-
timeless developer authored
-
- Jun 14, 2010
-
-
Greg Ward authored
Currently merge just prints abort-like messages to stderr and then exits with a misleading status 0 (cleverly disguised as "False"). With this change it raises Abort, just like every other fatal error.
-
- Jun 15, 2010
-
-
Greg Ward authored
It was left in just in case things went wrong with the tag cache in Mercurial 1.4, so we could easily crank up the verbosity with a one-line change. There have been no problems in 1.4 or 1.5, so it should be safe to drop this now.
-
Greg Ward authored
It was left behind just in case the tag cache blew up in Mercurial 1.4, so we could easily revert to the non-caching code. There have been no problems with the tag cache in 1.4 or 1.5, so it should be safe to get rid of this code now.
-
Christian Ebert authored
We can check for file existence in the working directory (needed in case of recording) by simply using the given context and calculate the manifest only when there are in fact candidates for expansion/shrinking.
-
- Jun 13, 2010
-
-
Georg Brandl authored
-
- Jun 15, 2010
-
-
Martin Geisler authored
-
- Jun 14, 2010
-
-
Frank Kingswood authored
-
Greg Ward authored
It tests that 'hg commit' does not crash if the user removes a newly added file, which has nothing to do with merging.
-
- Jun 15, 2010
-
-
Martin Geisler authored
-
Martin Geisler authored
-
Martin Geisler authored
-
Martin Geisler authored
-
Martin Geisler authored
The old check would only detect any/all at the beginning of a line. The regexp was probably just modeled after the preceding regexp which (correctly) finds the 'with' keyword at the beginning of a line. We now complain about 'any(' and 'all(' anywhere in a line, unless it is preceded by 'def'. This allows us to define our own compatibility wrapper in util and use 'util.any(' in the code.
-
- Jun 14, 2010
-
-
Renato Cunha authored
2to3 complains when relative and absolute imports are mixed, this fix just separates them on the zeroconf extension. According to 2to3, the other modules are fine.
-
- Jun 11, 2010
-
-
Matt Mackall authored
-
Martin Geisler authored
-
- Jun 10, 2010
-
-
Peter Arrenbrecht authored
Useful in tests to quickly build a complex DAG in an empty repo. Handles local tags and named branches. Options to, at each rev, - create a new file, - overwrite the same file, - append to the same file, - write to a specific line in a mergeable file. Can run shell commands during DAG buildup.
-
Peter Arrenbrecht authored
Mainly useful for reusing DAGs somewhere else, for example for attaching them to a bug report, or for importing them into other environments (like my test environment for incoming/outgoing discovery).
-
Peter Arrenbrecht authored
As discussed during the sprint. See the doc comment and doctests for specification and examples. This is used in subsequent patches to export revlog and changelog DAGs, and to generate a repo with a given changelog DAG.
-
Matt Mackall authored
-
Matt Mackall authored
-
- Jun 09, 2010
-
-
Julian Cowley authored
Gets the charset from encoding.encoding parameter.
-
Matt Mackall authored
-
- Jun 10, 2010
-
-
Chad Dombrova authored
python hooks are passed two new keyword arguments: - opts: a dict of options; unsepcified options are set to their default - pats: a list of arguments shell hooks receive two new variables containing string representations of the above data: - $HG_OPTS - $HG_PATS for example, the opts and pats for 'hg -f v1.1' would be: {'force': True, 'message': '', 'rev': '', 'user': '', 'date': '', 'local': None, 'remove': None, 'mq': None} ['v1.1']
-
- Jun 09, 2010
-
-
Matt Mackall authored
-
- Jun 07, 2010
-
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
This new configuration variable is similar in nature `ui.interactive', but applying to output instead of input. This allows as to support non-interactive sessions where formatted should be enabled, such as when using the pager extension. The variable itself is left undocumented; it is not intended for use outside Mercurial and its extensions.
-
- Jun 10, 2010
-
-
Martin Geisler authored
-
Sune Foldager authored
Previously #foo and --branch foo were handled identically. The behavior of #foo hasn't changed, but --branch now works like this: 1) If branchmap is not supported on the remote, the operation fails. 2) If branch is '.', substitute with branch of the working dir parent. 3) If branch exists remotely, its heads are expanded. 4) Otherwise, the operation fails. Tests have been added for the new cases.
-
- Jun 06, 2010
-
-
Katsunori FUJIWARA authored
this helps users to know what kind of option is: - no value is required(flag option) - value is required - value is required, and multiple occurrences are allowed each kinds are shown as below: -f --force force push -e --ssh CMD specify ssh command to use -b --branch BRANCH [+] a specific branch you would like to push if one or more 3rd type options are shown, explanation for '[+]' mark is also shown as footnote.
-
- Jun 09, 2010
-
-
Christian Ebert authored
Now that we have retrieved the context in every calling function except commit, pass it as argument to kwtemplater.overwrite to avoid looking it up twice. Reorder arguments to kwtemplater.overwrite to reflect their importance. Turn node argument into a simple boolean and rename it to iswctx.
-
- Jun 08, 2010
-
-
Peter Arrenbrecht authored
-
Gilles Moris authored
-
Gilles Moris authored
To avoid recurrent fixes for the display of this message, a summary table with all case combinations has been added to the code. Basically, there is two condition for the message to be printed: * this is not an initial (named branch or topo) root * none of the parents are in the current branch heads
-
Stefano Tortarolo authored
When a changeset is skipped, rebase keeps the previous target as next target and if the skipped cset is the first one, the recorded target is actually the original target. --abort did not detect this situation but simply stripped away the cset.
-
- Jun 09, 2010
-
-
Jan Sorensen authored
-