- Jun 07, 2010
-
-
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
-
Martin Geisler authored
-
Dirkjan Ochtman authored
-
- Jun 08, 2010
-
-
Matt Mackall authored
-
Steve Borho authored
-
Steve Borho authored
-
Thomas Arendsen Hein authored
Thanks to Greg Ward for spotting the problem introduced in 0a548640e012 and for supplying the test case.
-
Steve Borho authored
Initial config provided by Tim Pietzcker
-
Martin Geisler authored
-
Sune Foldager authored
-
Dirkjan Ochtman authored
-
Dirkjan Ochtman authored
-
- Jun 07, 2010
-
-
Dirkjan Ochtman authored
-
- Jun 04, 2010
-
-
Steve Borho authored
Some implementations of ui.label() (HTML versions in particular) must escape the provided text and then markup the text with their tags. When this marked up text is then passed to ui.write(), we must label the text as 'ui.labeled' so the implementation knows not to escape it a second time (exposing the initial markup). This required the addition of a 'ui.plain' label for text that is purposefully not marked up. I was a little pedantic here, passing even ' ' strings to ui.label() when it would be included with other labeled text in a ui.write() call. But it seemed appropriate to lean to the side of caution.
-
- Jun 07, 2010
-
-
Dirkjan Ochtman authored
-
Sune Foldager authored
-
Sune Foldager authored
The branch wasn't expanded, so only the tip was operated on.
-
- Jun 06, 2010
-
-
Pradeepkumar Gayam authored
-
Katsunori FUJIWARA authored
Mercurial has problem around text wrapping/filling in MBCS encoding environment, because standard 'textwrap' module of Python can not treat it correctly. It splits byte sequence for one character into two lines. According to unicode specification, "east asian width" classifies characters into: W(ide), N(arrow), F(ull-width), H(alf-width), A(mbiguous) W/N/F/H can be always recognized as 2/1/2/1 bytes in byte sequence, but 'A' can not. Size of 'A' depends on language in which it is used. Unicode specification says: If the context(= language) cannot be established reliably they should be treated as narrow characters by default but many of class 'A' characters are full-width, at least, in Japanese environment. So, this patch treats class 'A' characters as full-width always for safety wrapping. This patch focuses only on MBCS safe-ness, not on writing/printing rule strict wrapping for each languages MBCS sensitive textwrap class is originally implemented by ITO Nobuaki <daydream.trippers@gmail.com>.
-
- Jun 03, 2010
-
-
Christian Ebert authored
-
Adrian Buehlmann authored
-
Greg Ward authored
(There's still a chmod() call to manually preserve the mode of the data file.)
-
- Jun 05, 2010
-
-
Matt Mackall authored
-
Matt Mackall authored
-
Matt Mackall authored
-
Matt Mackall authored
-
Matt Mackall authored
-
Matt Mackall authored
-
Matt Mackall authored
-