- Jan 16, 2014
-
-
Simon Heimberg authored
Test for failing matches and warnings. (The existing test-run-tests.t can not do both by design.) And simulate matching on other os.
-
- Jan 09, 2014
-
-
Pierre-Yves David authored
The main goal is to monitor that working directory parent are correct after backout. This will be useful the next changeset introducting magic merge usage.
-
- Dec 01, 2013
-
-
Katsunori FUJIWARA authored
Before this patch, transplant extension shows the list of available responses by specific string, even though the prompt string passed to "ui.promptchoice()" has enough (maybe i18n-ed) information. This patch uses "ui.extractchoices()" to show the list of available responses.
-
Katsunori FUJIWARA authored
Before this patch, transplant extension uses "ui.prompt()" for interactive transplant, and has to check whether user response returned by "ui.prompt()" is valid or not in own code. In addition to it, transplant extension uses response characters (e.g. "y", "n", and so on) directly in own code, and this disallows to use another response characters by translation, even though the help shown by '?' typing is translatable. This patch uses "ui.promptchoice()" instead of "ui.prompt()" to resolve problems above.
-
Katsunori FUJIWARA authored
-
Katsunori FUJIWARA authored
Before this patch, record extension gets the list of available responses from online help document of "hg record" in the tricky way, even though the value passed to "ui.promptchoice()" has enough (maybe i18n-ed) information. This patch uses "ui.extractchoices()" to get the list of available responses.
-
Katsunori FUJIWARA authored
-
- Jan 06, 2014
-
-
Pierre-Yves David authored
We are doing membership test and substraction. new code is marginally faster.
-
Pierre-Yves David authored
We drop iterrevs which are not needed anymore. The know head are never a descendant of the updated set. It was possible with the old strip code. This simplification make the code easier to read an update.
-
- Jan 04, 2014
-
-
Pierre-Yves David authored
We never use the node of new revisions unless in the very specific case of closed heads. So we can just use the revision number. So give another handfull of percent speedup.
-
- Jan 15, 2013
-
-
Pierre-Yves David authored
Now that no user try to update the cache on a truncated repo we can drop the extra lookup. Give an handfull percent speedup on big branchmap update.
-
- Jan 04, 2014
-
-
Pierre-Yves David authored
The line fit in 80 character limit without it. It is even shorter without it.
-
- Jan 16, 2014
-
-
Simon Heimberg authored
This does not happen when running normal. But when fiddling around with the test infrastructure, this helps a lot. Old traceback messge Exception in thread Thread-7: Traceback (most recent call last): ... new traceback message Exception in thread test-something.t: Traceback (most recent call last): ...
-
Simon Heimberg authored
Before no message was returned to the main thread. No result was registered and no new thread was started. This does not happen when running normal. But when fiddling around with the test infrastructure, this helps a lot.
-
- Jan 07, 2014
-
-
Takumi IINO authored
-
- Jan 16, 2014
-
-
durin42 authored
-
- Jan 07, 2014
-
-
Takumi IINO authored
-
Takumi IINO authored
-
Takumi IINO authored
Infinity scroll is broken when you override the web.style in the following ways: $ hg --config='web.style=gitweb' serve $ open http://localhost:8080/shortlog?style=paper ajaxScrollInit should use http://localhost:8080/shortlog/%next%?style=paper. however, http://localhost:8080/shortlog/%next% is used actually. It is missing style parameter. This patch add style parameter to request url.
-
Takumi IINO authored
Some styles have indentation.
-
- Nov 16, 2013
-
-
Mads Kiilerich authored
-
Mads Kiilerich authored
-
- Nov 17, 2013
-
-
Mads Kiilerich authored
Before it just said 'nothing to rebase'. Now 'if "base" is an empty set: abort: empty "base" revision set - can't compute rebase set If the set of changesets to rebase can't be found from "base", it will fail as before but with more explanation of what the problem was. The name of the "base" option is not obvious - it is more like "samples identifying the branch to rebase". The error messages for problems with the specified "base" value will use that term and might thus also not be obvious, but at least they are consistent with the option name. The name "base" will not be used if the base only was specified implicitly as the working directory parent.
-
Mads Kiilerich authored
Before, it just said 'nothing to rebase' in this case. Now, it aborts mentioning the reason: 'empty "source" revision set'. Specifying revisions that cannot be rebased is a 'soft' error, but specifying an empty set deserves an abort that explains exactly what the problem is.
-
- Nov 16, 2013
-
-
Mads Kiilerich authored
Before, it just said 'nothing to rebase' in this case. Now, it aborts mentioning the reason: 'empty "rev" revision set'. Specifying revisions that cannot be rebased is a 'soft' error, but specifying an empty set deserves an abort that explains exactly what the problem is.
-
- Nov 17, 2013
-
-
Mads Kiilerich authored
-
- Nov 21, 2013
-
-
Mads Kiilerich authored
Was the behavior correct and the description wrong so it should be updated as in this patch? Or should the code work as the documentation says? Both ways could make some sense ... but none of them are obvious in all cases. One place where it currently cause problems is when the current revision has another branch head that is closer to tip but closed. 'hg rebase' refuses to rebase to that as it only see the tip-most unclosed branch head which is the current revision. /me kind of likes named branches, but no so much how branch closing works ...
-
- Jan 12, 2014
-
-
Mads Kiilerich authored
This is often very handy when hacking/debugging. Calling util.debugstacktrace('hey') from a place in hg will give something like: hey at: ./hg:38 in <module> /home/user/hgsrc/mercurial/dispatch.py:28 in run /home/user/hgsrc/mercurial/dispatch.py:65 in dispatch /home/user/hgsrc/mercurial/dispatch.py:88 in _runcatch /home/user/hgsrc/mercurial/dispatch.py:740 in _dispatch /home/user/hgsrc/mercurial/dispatch.py:514 in runcommand /home/user/hgsrc/mercurial/dispatch.py:830 in _runcommand /home/user/hgsrc/mercurial/dispatch.py:801 in checkargs /home/user/hgsrc/mercurial/dispatch.py:737 in <lambda> /home/user/hgsrc/mercurial/util.py:472 in check ...
-
- Jan 07, 2014
-
-
Simon Heimberg authored
-
Simon Heimberg authored
Using check-code-ignore to skip the failures on a line has several disadvantages: * It skips all check-code failures on a line, not only the one it was created for. * It does not give any hint for which rule it was added, making it difficult to see when it is not needed anymore. So drop this pragma in favor of better alternatives promoted before.
-
Simon Heimberg authored
In the past several approaches were used when a check-code rule triggered without a good reason. Not all of them looked nice, some were even wrong. Suggest some good practices which should be used instead.
-
Simon Heimberg authored
Use the work-around suggested by the rule instead
-
Simon Heimberg authored
Skipping an entire file generally from checking is an important event, so report it always. Do not tell the check name because skipping does not depend on it. Directly skip the entire file instead of checking more patterns and skip again. The pragma no-check-code was introduced by accident in the past. (Fixed in e033a7d444ac and ee07f9d142c9.) This now is prevented because the files to skip have to be listed in the test output of test-check-code-hg.t.
-
Simon Heimberg authored
Skipping of the entire file has been introduced in bc3b48b0f5c8.
-
- Nov 16, 2013
-
-
Mads Kiilerich authored
14913fcb30c6 not only introduced the 'bisect(current)' revset predicate, it also changed how the 'current' revision is used in combination with --command. The new behaviour might be ok for --noupdate where the working directory and its revision shouldn't be used, but it also did that when --command is used to run a command on the currently checked out revision then it could register the test result on the wrong revision. An example: Before, bisect with --command could use the wrong revision when recording the test result: $ hg up -qr 0 $ hg bisect --command "python \"$TESTTMP/script.py\" and some parameters" changeset 31:58c80a7c8a40: bad abort: inconsistent state, 31:58c80a7c8a40 is good and bad Now it works as before and as expected and uses the working directory revision for the --command result: $ hg up -qr 0 $ hg bisect --command "python \"$TESTTMP/script.py\" and some parameters" changeset 0:b99c7b9c8e11: bad ...
-
Mads Kiilerich authored
The 'copies' method has no test coverage and calls copies.pathcopies with an incorrect number of parameters and is thus (fortunately) not used. Kill it.
-
- Nov 19, 2013
-
-
Siddharth Agarwal authored
This isn't used outside this block, nor is it expected to be.
-
Siddharth Agarwal authored
This is more correct because we now fetch '.' while nothing else can interfere with it.
-
- Nov 22, 2013
-
-
Siddharth Agarwal authored
cur will be moved inside the wlock in a future patch, so we need to pass it into checkconflict explicitly.
-
- Nov 19, 2013
-
-
Siddharth Agarwal authored
Any invocations of bookmarks other than a plain 'hg bookmarks' will likely cause a write to the bookmark store. These should be guarded by the wlock. The repo._bookmarks read should be similarly guarded by the wlock if we're going to be subsequently writing to it.
-