- Nov 16, 2011
-
-
kiilerix authored
-
- Nov 15, 2011
-
-
Matt Mackall authored
-
Matt Mackall authored
We used to use os.path.normcase which was a no-op, which was unhelpful for cases like VFAT on Linux.
-
Thomas Arendsen Hein authored
54c0517c0fe8 introduced a new block in test-convert-bzr-directories.t which produces a slightly different output with older bzr versions. Tested with bzr 1.5 on Debian lenny.
-
- Nov 10, 2011
-
-
Pierre-Yves David authored
-
Pierre-Yves David authored
-
Pierre-Yves David authored
-
Pierre-Yves David authored
-
Pierre-Yves David authored
The advanceboundary documentation is updated to highlight the difference.
-
Pierre-Yves David authored
This rename prepare the creation of retract boundaru that move boundary backward
-
Pierre-Yves David authored
-
Matt Mackall authored
-
Matt Mackall authored
-
Matt Mackall authored
-
Matt Mackall authored
-
Matt Mackall authored
-
David M. Carr authored
Change the behavior of the forget command such that explicit paths in subrepos are handled by forgetting the file in the subrepo. This eliminates the previous behavior where if you called "hg forget" for an explicit path in a subrepo, it would state that the file is already untracked.
-
David M. Carr authored
Adds a section to test-subrepo.t that demonstrates the current behavior when you pass the full path to a file in a subrepo to hg forget.
-
Katsunori FUJIWARA authored
"hg status" may treat cache missed largefiles as "removed" incorrectly. assumptions for problem case: - there is no cache for largefile "L" - at first, update working directory to the revision in which "L" is not yet added, - then, update working directory to the revision in which "L" is already added and now, "hg status" treats "L" as "removed". current implementation does not allocate entry for cache missed largefile in ".hg/largefiles/dirstate", but files without ".hg/largefiles/dirstate" entry are treated as "removed" by largefiles extension. "hg revert" can not recover from this situation, but "rm -rf .hg/largefiles", because it causes dirstate rebuilding. this patch invokes normallookup() for cache missed largefiles to allocate entry in ".hg/largefiles/dirstate", so "hg status" can treat it as "missing" correctly.
-
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
-