- 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
-
Alexander Plavin authored
-
Alexander Plavin authored
-
Alexander Plavin authored
-
Alexander Plavin authored
-
Alexander Plavin authored
-
Alexander Plavin authored
-
Alexander Plavin authored
-
Alexander Plavin authored
-
- Jul 18, 2013
-
-
Matt Mackall authored
-
- Jul 14, 2013
-
-
Wei, Elson authored
-
Wei, Elson authored
-
- Jul 12, 2013
-
-
Wei, Elson authored
-
Wei, Elson authored
-
- Jul 11, 2013
-
-
Jordi Gutiérrez Hermoso authored
At the moment, creating secret commits is slightly cumbersome. They can either be created by changing the default commit phase to secret or by doing `hg phase --secret --force`. Both of these make secret commits appear to be like some kind of advanced feature. Secret commits, however, should be a convenient feature for people who want to work on a private branch without affecting anyone else. There should therefore be a prominent and convenient method for creating secret commits. Since the default phase is draft and there is no need to use --force to go from a secret phase to any other phase, this patch intentionally does not add --draft and --public options.
-
- Jul 17, 2013
-
-
Florence Laguzet authored
The --force option in merge does not make what people think it does so it may not be visible to everyone. I have local changes and want to pull one's changes which made 2 heads. The --force option in help says -f --force force a merge with outstanding changes so I can expect that I can use it to force the merge and commit it in my local repository without taking my local changes into account. But merging with -f keeps local changes and "add" them: they must be committed or reverted before doing the merge commit. The merge -f cannot be reverted so it leads my repository in a bad state: cannot commit merge and don't want to revert/commit local changes yet. Message in help have been updated to emphasize the fact that local changes are included in the merge.
-
- Jul 18, 2013
-
-
Brendan Cully authored
-
Brendan Cully authored
-
- Jul 11, 2013
-
-
Alexander Plavin authored
Before this when multiple changesets hashes in the repos started with the search query string, error was given that the revision isn't found, and it was misleading. Now a simple keyword search runs in this case.
-
- Jul 18, 2013
-
-
Siddharth Agarwal authored
-
Siddharth Agarwal authored
-
- Jul 12, 2013
-
-
Alexander Plavin authored
-
Alexander Plavin authored
This gives all the benefits introduced before for file source view, namely code selection without line numbers and correct indents, highlighting line which is linked to, long lines wrapping. Implementation strategy is also the same as for file source view: all the lines are put in a sigle pre tag with span's for each line. Correct line numbering (same as before this patch) is achieved with nested CSS counters.
-