- May 18, 2015
-
-
Matt Harbison authored
-
Matt Harbison authored
-
- May 16, 2015
-
-
Augie Fackler authored
-
Augie Fackler authored
-
Augie Fackler authored
-
Augie Fackler authored
any() is available in all Python versions we support now.
-
Augie Fackler authored
-
- May 18, 2015
-
-
Pierre-Yves David authored
Again, this make the code clearer.
-
Pierre-Yves David authored
The 'next()' built-in accept a default value. This remove the needs to check if self non-empty before returning a value.
-
Pierre-Yves David authored
The 'next()' built-in can return a default value, allow to get rid of the confusing try/except code flow.
-
Pierre-Yves David authored
The 'next()' built-in can return a default value, allow to get rid of the confusing try/except code flow.
-
Pierre-Yves David authored
The 'next()' built-in can return a default value, making the final iteration case simpler and clearer.
-
Pierre-Yves David authored
'next' is supported by Python2.6 the new lowest version supported by Mercurial.
-
Pierre-Yves David authored
'isdisjoint' is available in Python 2.6. The new lowest supported version.
-
Pierre-Yves David authored
Using 'classs foo():' result in old style object instead of new style object. We do not want old style object so this check is unrelated to 2.4.
-
Pierre-Yves David authored
This is available in Python2.6 the new default supported release.
-
Pierre-Yves David authored
It is already imported a couple of line above.
-
Augie Fackler authored
-
- May 15, 2015
-
-
Anton Shestakov authored
-
Anton Shestakov authored
-
Anton Shestakov authored
-
Anton Shestakov authored
-
Anton Shestakov authored
Browse (or manifest) action allows browsing the directory structure at some specified revision. In gitweb and monoblue styles, the revision header already has branch/tag/bookmark information for the revision, but in paper style this header was only showing tags. This patch adds branches and bookmarks. Branch name needs to be obtained in this special way to be consistent with regular changeset page, where in paper style default branch is never shown.
-
- May 16, 2015
-
-
Yuya Nishihara authored
It never uses self, so let's make it less dependent on variables.
-
Yuya Nishihara authored
-
- Mar 30, 2015
-
-
Yuya Nishihara authored
Since 5548f558db3d, it should no longer be necessary because the addset can remove duplicates correctly.
-
- May 10, 2015
-
-
Pierre-Yves David authored
The 'bundlecaps' argument is built as a set, we need to stabilise the order before exchanging them. Otherwise, in the test, http logs are unstable when the 'bundlecaps' contains something (eg: using bundle2).
-
Pierre-Yves David authored
We now have a lock triggered for any transaction. We use it to ensure no-read are made in read-only mode. We need more that just "no changegroup is added", since bundle2 allows for more than just changegroup to be exchanged. We still protect pushkey as it may write data without opening a transaction.
-
Pierre-Yves David authored
The locking scheme is a bit different in each cases. So we explicitly test each case.
-
Pierre-Yves David authored
When the progress extension is not enabled, each call to 'ui.progress' used to issue a debug message. This results is a very verbose output and often redundant in tests. Dropping it makes tests less volatile to factor they do not meant to test. We had to alter the sed trick in 'test-rename-merge2.t'. Sed is used to drop all output from a certain point and hidding the progress output remove its anchor. So we anchor on something else.
-
- May 15, 2015
-
-
Anton Shestakov authored
As for the gitweb style, this line for filelogentry template is copied from shortlogentry. No change to python code is needed. Tests are unaffected.
-
Anton Shestakov authored
This line for filelogentry template is copied from shortlogentry. The information is already displayed in paper style, so no change to python code is needed. Tests are unaffected.
-
- May 16, 2015
-
-
Matt Harbison authored
This will work for any command that creates its matcher via scmutil.match(), but only the files command is tested here (both workingctx and basectx based tests). The previous behavior was to completely ignore the files in the subrepo, even though -S was given. My first attempt was to teach context.walk() to optionally recurse, but once that was in place and the complete file list was built up, the predicate test would fail with 'path in nested repo' when a file in a subrepo was accessed through the parent context. There are two slightly surprising behaviors with this functionality. First, any path provided inside the fileset isn't narrowed when it is passed to the subrepo. I dont see any clean way to do that in the matcher. Fortunately, the 'subrepo()' fileset is the only one to take a path. The second surprise is that status predicates are resolved against the subrepo, not the parent like 'hg status -S' is. I don't see any way to fix that either, given the path auditor error mentioned above.
-
Matt Harbison authored
This will be used in the next patch to help matchers resolve filesets in subrepos. The default implementation returns an empty set (for git and svn).
-
- May 15, 2015
-
-
Gilles Moris authored
-
- Apr 13, 2015
-
-
Martin von Zweigbergk authored
It should be possible to debug the submanifest revlogs without having to know where they are stored (in .hg/store/meta/), so let's add a --dir option for this purpose.
-
- May 10, 2015
-
-
Pierre-Yves David authored
Because bundle2 allows a more precise exchange of obsmarkers during pull, it sends them in a different order (previously unstable because of sets.) As a result, they are added to the repository in a different order. To stabilize the order and ensure tests are unchanged when moving from bundle1 to bundle2 we sort markers when exchanging them. In the long run, the obsstore will probably not use a linear storage.
-
- Apr 21, 2015
-
-
Pierre-Yves David authored
We need to disable the "bundle2" capability to ensure we stay on legacy capability.
-
Pierre-Yves David authored
We need to disable the "bundle2" capability to ensure we stay on legacy capability.
-
- May 15, 2015
-
-
Pierre-Yves David authored
Before this change, doing ordered iteration over an 'addset' object composed of operands without fastasc or fastdesc method could result in duplicated entries. This was the result of applying '_iterordered' on an unordered set. We fix it by ensuring we iterate over the set in a sorted order. Using the fast iterator when it exists on any operand. We kill the '_iterator' method in the process because it did not make a lot of sense independently. Thanks goes to Yuya Nishihara for reporting the issue and analysing the cause.
-