- Jul 25, 2013
-
-
Matt Mackall authored
-
- Jul 21, 2013
-
-
Alexander Plavin authored
This fixes issue3990 for Webkit-browsers, and also older Opera versions. Rendering in firefox is not changed.
-
- Jul 20, 2013
-
-
Alexander Plavin authored
Given that N is maximum revision number in a repo, than if a revision with number N-100n or N-100n+1 (for any integer n) is found with a hgweb search, this revision is duplicated in search results.
-
- Jul 24, 2013
-
-
durin42 authored
We can't (easily) force SSL version on older Pythons, but on 2.6 and later we can force SSLv3, which is safer and widely supported. This also appears to work around a bug in IIS detailed in issue 3905.
-
durin42 authored
Includes upstream change "socketutil: force SSLv3 by default, as it is safer" which should fix issue 3905.
-
- May 12, 2013
-
-
durin42 authored
Not all WSGI servers close the socket when an early response is sent to a large POST request, which can cause the server to interpret the already-sent request body as an incoming (but hopelessly invalid) request.
-
- Jul 24, 2013
-
-
Alexander Plavin authored
Actual amount of revisions is used now instead of their numbers in the repo before to deal with skipped numbers correctly.
-
Alexander Plavin authored
Actual amount of revisions is used now instead of their numbers in the repo before to deal with skipped numbers correctly. This iterates starting from the newest revision (which is shown on top) yielding up to the specified count, instead of the reversed order used before. Effect of this change on efficiency is negligible, when the same changesets are returned.
-
Alexander Plavin authored
It is the same fix for graph command, as was recently for log. This makes the specified revision be always on top of the graph view. Before the patch, for example with repo having revisions 0, 1, 2, 3 and revision in url being '2', all revisions were shown and the specified one wasn't the first.
-
- Jul 25, 2013
-
-
Matt Mackall authored
-
- Jul 24, 2013
-
-
Wagner Bruna authored
-
- Jul 25, 2013
-
-
Matt Mackall authored
This takes advantage of the new checkunfinished infrastructure
-
Matt Mackall authored
-
Matt Mackall authored
Nobody loves transplant anymore, but it was the first command to have a --continue flag.
-
Matt Mackall authored
The tests contain a couple corner cases where workarounds are now required. Strictly speaking, these are behavior regressions, but of an extremely obscure and marginal sort. Commits or updates in the middle of a histedit would have almost always been fairly serious user error.
-
Matt Mackall authored
-
Matt Mackall authored
This could cause a rebase to be 'in progress' even though it aborted.
-
Matt Mackall authored
commands checked: backout bisect commit graft import
-
Matt Mackall authored
Unclearable operations will cause an abort.
-
Matt Mackall authored
This adds a registration point and check functions that will allow commands to check if multistep operations like an interrupted graft or rebase are in progress before proceeding.
-
- Jul 24, 2013
-
-
durin42 authored
-
Wei, Elson authored
-
- Jul 23, 2013
-
-
Matt Mackall authored
Looking up hidden prefixes could cause a no node exception Looking up unique non-hidden prefixes could be ambiguous
-
Matt Mackall authored
This was documented, but not implemented.
-
- Jul 21, 2013
-
-
Matt Mackall authored
The old docs emphasized topological heads rather than branch heads and incorrectly defined branch heads as not having children rather than descendants.
-
- Jul 19, 2013
-
-
Matt Mackall authored
-
Matt Mackall authored
-
Matt Mackall authored
-
- Jul 12, 2013
-
-
Shun-ichi GOTO authored
This change treat the ESRCH error as ENOENT like WindowsError class does in python 2.5 or later. Without this change, some try..execpt code which expects errno is ENOENT may fail. Actually hg command does not work with python 2.4 on Windows. CreateFile() will fail with error code ESRCH when parent directory of specified path is not exist, or ENOENT when parent directory exist but file is not exist. Two errors are same in the mean of "file is not exist". So WindowsError class treats error code ESRCH as ENOENT in python 2.5 or later, but python 2.4 does not. Actual results with python 2.4: >>> errno.ENOENT 2 >>> errno.ESRCH 3 >>> WindowsError(3, 'msg').errno 3 >>> WindowsError(3, 'msg').args (3, 'msg') And with python 2.5 (or later): >>> errno.ENOENT 2 >>> errno.ESRCH 3 >>> WindowsError(3, 'msg').errno 2 >>> WindowsError(3, 'msg').args (3, 'msg') Note that there is no need to fix osutil.c because it never be used with python 2.4.
-
- Jul 17, 2013
-
-
Matthew Turk authored
This splits churn email aliases from the right, to enable incorrectly-specified addresses that include equal signs to be mapped to correct addresses. This will enable aliasing of bad addresses (typically typos) such as: sername=myusername that appear in the churn output through a churn alias such as: sername=myusername = myusername whereas previously splitting from the left would not enable this behavior.
-
- Jul 14, 2013
-
-
Alexander Plavin authored
-
- Jul 12, 2013
-
-
Alexander Plavin authored
This makes the specified revision be always on top of the list. Before the patch, for example with repo having revisions 0, 1, 2, 3 and user searching for '2', all revisions were shown and the specified one wasn't the first.
-
- Jul 01, 2013
-
-
Simon Heimberg authored
-
- Jul 19, 2013
-
-
Matt Mackall authored
It made the windows buildbot sad.
-
- Jul 13, 2013
-
-
Alexander Plavin authored
-
Alexander Plavin authored
This changes line highlight color from a fain yellow (#ffff99) to a faint blue (#bfdfff), because yellow color is used in comparison view for inserted lines. This new color is okay for people with different forms of color blindness (tested with a simulator): a) this color looks quite different from other used backgrounds b) text doesn't lose distinction on this color
-
- Jul 18, 2013
-
-
Mads Kiilerich authored
The 'copynode' was looked up in self.keep as if it was a changeset node. It is however a filelog node, and self.keep would thus fail if it actually looked at its parameter ... which it only did if a startrev was specified. Instead we now don't check the copy node - we don't have to. It must have been copied from one of the parents, and we already check whether one of the parents have the copy source. We could perhaps use linkrev to see if the corresponding changeset was converted ... but that would sometimes be wrong. The existing test of this was wrong - now it is better, but it seems like it exposes a 'log' issue.
-
Mads Kiilerich authored
The test assumed that 'b' was missing just because the changeset that introduced 'b' wasn't converted ... but 'b' was also not removed before the start revision, and the parent was thus not missing at all. Instead we introduce a file 'f' in rev 0 and remove it in rev 1 so the copy source really doesn't exist in the repo that is converted from rev 1.
-
- Jul 13, 2013
-
-
Alexander Plavin authored
-
Alexander Plavin authored
-