- Sep 26, 2010
-
-
Matt Mackall authored
-
- Sep 25, 2010
-
-
kiilerix authored
Solaris false returns 255 instead of 1, so we remove one unneeded instance and replaces another with (exit 1) as suggested by Brodie Rao.
-
kiilerix authored
Solaris diff gives @@ -1,1 +1,1 @@ instead of @@ -1 +1 @@
-
kiilerix authored
Cleanup in 22f3353bcc36 removed a syntactically incorrect and apparently unnecessary escape of / for expr - but solaris needs it.
-
kiilerix authored
Solaris do not know the service called http, so we use echo instead. Trying to define KILLQUIETLY when running the hgserve function didn't set the value within the function. Now we set the variable before calling the function.
-
- Sep 21, 2010
-
-
Dan Villiom Podlaski Christiansen authored
-
- Sep 24, 2010
-
-
Matt Mackall authored
-
Erik Zielke authored
Incoming and outgoing are fixed so they go through the whole three of repositories instead of only visiting first level of sub repositories.
-
Martin Geisler authored
Many tests already had a short line to describe what IssueXXX is about. I find that quite useful when reading a test.
-
kiilerix authored
-
kiilerix authored
Solaris had problems with zh_CN and warned "couldn't set locale correctly" on stderr. We don't care.
-
kiilerix authored
It seems like ln -s gets confused if an existing symlink is dangling: $ rm -f a b; ln -s a b; ln -sf b b ln: cannot create b: File exists We now rely on rm instead of on ln -sf.
-
kiilerix authored
Backport 3acd5f7ab9d0 and 9581d5efb6a5 to stable.
-
- Sep 23, 2010
-
-
Patrick Mezard authored
-
Patrick Mezard authored
-
Patrick Mezard authored
_bookmarks is loaded lazily and calls super.lookup(). Unfortunately, branch and tags caches initializations also recurse in lookup() and end up trying to access _bookmarks again. Massive confusion ensues. I considered fixing all branches and tags cache loading to avoid recursing in lookup() but it would add complexity to otherwise working code provided lookups are performed on nodes or revnums.
-
Alexandre Fayolle authored
When using hg commands over an http repository in a long running process, a httphandler instance is leaked for each command, because of a loop handler.parent -> OpenerDirector and OpenerDirector.handlers -> handler which is not handled by Python's gc. Discussion on #mercurial concluded that removing the __del__ method solved the problem.
-
Christian Ebert authored
-
- Sep 22, 2010
-
-
Erik Zielke authored
-
Erik Zielke authored
The old asciidoc format supported something like this, this is why there is NOTE: scattered here and there.
-
- Sep 23, 2010
-
-
Brodie Rao authored
-
Martin Geisler authored
-
Brodie Rao authored
-
Anthony Foiani authored
-
- Sep 22, 2010
-
-
kiilerix authored
-
kiilerix authored
f786fc4b8764 assumed that walkchangerevs called prep with all relevant matched filenames, but actually it only contains the names of files changed in the relevant changeset. That meant that log diff/stat of merges missed the diff for files only changed in the other branch. This is a minimal fix for making sure we only use fns when we are following and thus will have problems with merges anyway ...
-
kiilerix authored
01-01-1980 slipped through the grep.
-
Matt Mackall authored
-
Matt Mackall authored
-
Patrick Mezard authored
--force was not necessary when passing --rev since 55578a8d7e84, but this behaviour is usually harmful when branch names are passed instead of explicit revisions.
-
Matt Mackall authored
-
Brodie Rao authored
This adds a " (glob)" marker that works like a simpler version of (re): "*" is converted to ".*", and "?" is converted to ".". Both special characters can be escaped using "\", and the backslash itself can be escaped as well. Other glob-style syntax, like "**", "[chars]", or "[!chars]", isn't supported.
-
Brodie Rao authored
Consider this test: $ hg glog --template '{rev}:{node|short} "{desc}"\n' @ 2:20c4f79fd7ac "3" | | o 1:38f24201dcab "2" |/ o 0:2a18120dc1c9 "1" Because each line beginning with "|" can be compiled as a regular expression (equivalent to ".*|"), they will match any output. Similarly: $ echo foo The blank output line can be compiled as a regular expression and will also match any output. With this patch, none of the above output lines will be matched as regular expressions. A line must end in " (re)" in order to be matched as one. Lines are still matched literally first, so the following will pass: $ echo 'foo (re)' foo (re)
-
Brodie Rao authored
Regular expressions in the test suite are currently written assuming that you need a trailing ".*" to avoid matching to the end. Instead of matching regular expressions using "^pattern", this patch makes matching more restrictive by matching "^pattern$".
-
Brodie Rao authored
Currently, the following unified test will pass: $ echo foo A blank output line (a line containing just two spaces) will match any output. The patch modifies the unified test runner to ignore empty strings strings when do regular expression matching.
-
Brodie Rao authored
-
- Sep 21, 2010
-
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
- Sep 06, 2010
-
-
Peter Arrenbrecht authored
This speeds up merges of lots of files considerably.
-
- Sep 22, 2010
-
-
Matt Mackall authored
-