- Nov 10, 2011
-
-
Matt Mackall authored
-
Matt Mackall authored
-
- Nov 08, 2011
-
-
Stefano Tortarolo authored
This could happen in specific situations in which 'target' was selected as external and used for p1 _and_ p2.
-
- Nov 10, 2011
-
-
Matt Mackall authored
-
- Nov 09, 2011
-
-
Martin Geisler authored
-
Martin Geisler authored
-
Martin Geisler authored
-
- Nov 06, 2011
-
-
Stefano Tortarolo authored
When storing/restoring a nullmerge (-2), a 'standard' conversion was made and an existing changeset was wrongly used. Nullmerge should instead be treated as a special case.
-
- Nov 08, 2011
-
-
Stefano Tortarolo authored
-
- Nov 10, 2011
-
-
Nicolas Venegas authored
Prior to this patch "hg diff -U0", i.e., zero lines of context, would output hunk headers with a start line one greater than what GNU patch and git output. Guido van Rossum documents the unified diff format[1] as having a start line value "one lower than one would expect" for zero length hunks. Comparing the behaviour of the three systems prior to this patch in transforming c1 c3 to c1 c2 c3 - GNU "diff -U0" reports the hunk as "@@ -1,0 +2 @@" - "git diff -U0" reports the hunk as "@@ -1,0 +2 @@" - "hg diff -U0" reports the hunk as "@@ -2,0 +2,1 @@" After this patch, "hg diff -U0" reports "@@ -1,0 +2,1 @@". Since "hg export --config diff.unified=0" outputs zero-context unified diffs, "hg import" has also been updated to account for start lines one less than expected for zero length hunk ranges. [1]: http://www.artima.com/weblogs/viewpost.jsp?thread=164293
-
- Nov 08, 2011
-
-
Patrick Mezard authored
With renames like: a -> b a/c -> a/c We were ignoring or duplicating the second one instead of leaving files unchanged or moving them to their proper destination only. To avoid this, we process the files in reverse lexicographic order, from most to least specific change, and ignore files already processed. v2: - Add a test - Change "reverse=1" into "reverse=True"
-
- Nov 01, 2011
-
-
Simon Heimberg authored
-
Simon Heimberg authored
When pure is specified ext_modules is emptied in hgbuildpy.finalize_options. Before this happens has_ext_modules returned True.
-
- Jul 23, 2011
-
-
Simon Heimberg authored
-
- Nov 09, 2011
-
-
Matt Mackall authored
-
- Nov 07, 2011
-
-
Pierre-Yves David authored
We filter unknown node out of the boundary. No data is lost. A filtering is explicitly done after strip too
-
Pierre-Yves David authored
-
Pierre-Yves David authored
Also include logic to detect when to write phases data.
-
Pierre-Yves David authored
* force recompute of outdated cache * handle nullrev case
-
kiilerix authored
':' has no special meaning in paths, so there is no need for encoding it. Not encoding ':' makes it easier to test on windows.
-
kiilerix authored
-
kiilerix authored
-
kiilerix authored
-
kiilerix authored
-
kiilerix authored
Globbing is usually used for filenames, so on windows it is reasonable and very convenient that glob patterns accepts '\' or '/' when the pattern specifies '/'.
-
kiilerix authored
-
kiilerix authored
-
kiilerix authored
-
kiilerix authored
chmod of helper scripts is not included. tests that exercise the x bit in the file system uses 'hghave execbit'.
-
kiilerix authored
-
kiilerix authored
-
kiilerix authored
debugstate would always report files as mode 666 or 777 on Windows. umask is not used on Windows, but faking and using a defalt value of 022 matches what the test suite uses on Unix.
-
kiilerix authored
The exit code returned from a program to the shell is unsigned 8-bit, but Mercurial would sometimes try to exit with negative numbers or None. sys.exit on Unix will convert that to 8-bit exit codes, but on Windows negative values showed up as 0. The exit code is now explicitly converted to unsigned 8-bit.
-
kiilerix authored
Windows agree that it was Thu Jan 01 00:00:00 1970 +0000 but it also claims that it was Thu Dec 31 23:59:59 1969 -0000
-
kiilerix authored
Subrepo diffs would sometimes use backslash on windows.
-
kiilerix authored
-
kiilerix authored
The code for match on (esc) lines didn't work, and it would thus always end up emitting another suggestion ... which however would match the old one.
-
Matt Mackall authored
Normally changes in tests are reported like this in diffs: $ cat foo - a + b Using -i mode lets us update tests when the new results are correct and/or populate tests with their output. But with the standard doctest framework, inline Python sections in tests changes instead result in a big failure report that's unhelpful. So here, we replace the doctest calls with a simple compile/eval loop.
-
Matt Mackall authored
-
- Nov 04, 2011
-
-
Martin Geisler authored
-