Wed, 22 Sep 2010 23:51:10 +0200 mq: always require --force when pushing patches (issue2363) stable
Patrick Mezard <pmezard@gmail.com> [Wed, 22 Sep 2010 23:51:10 +0200] rev 12378
mq: always require --force when pushing patches (issue2363) --force was not necessary when passing --rev since 55578a8d7e84, but this behaviour is usually harmful when branch names are passed instead of explicit revisions.
Wed, 22 Sep 2010 18:20:47 -0500 tests: various fixes for new unified test pattern format
Matt Mackall <mpm@selenic.com> [Wed, 22 Sep 2010 18:20:47 -0500] rev 12377
tests: various fixes for new unified test pattern format
Wed, 22 Sep 2010 16:06:02 -0500 tests: add glob matching for unified tests
Brodie Rao <brodie@bitheap.org> [Wed, 22 Sep 2010 16:06:02 -0500] rev 12376
tests: add glob matching for unified tests 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.
Wed, 22 Sep 2010 16:06:00 -0500 tests: require regexes in unified tests to be marked with " (re)"
Brodie Rao <brodie@bitheap.org> [Wed, 22 Sep 2010 16:06:00 -0500] rev 12375
tests: require regexes in unified tests to be marked with " (re)" 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)
Wed, 22 Sep 2010 16:05:59 -0500 tests: ensure regexes match to the end of the string
Brodie Rao <brodie@bitheap.org> [Wed, 22 Sep 2010 16:05:59 -0500] rev 12374
tests: ensure regexes match to the end of the string 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$".
Wed, 22 Sep 2010 16:05:59 -0500 tests: don't match blank output lines as regexes in unified tests
Brodie Rao <brodie@bitheap.org> [Wed, 22 Sep 2010 16:05:59 -0500] rev 12373
tests: don't match blank output lines as regexes in unified tests 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.
Wed, 22 Sep 2010 16:05:58 -0500 tests: improve regexes in unified tests
Brodie Rao <brodie@bitheap.org> [Wed, 22 Sep 2010 16:05:58 -0500] rev 12372
tests: improve regexes in unified tests
Wed, 22 Sep 2010 00:14:57 +0200 templater: add hex filter.
Dan Villiom Podlaski Christiansen <danchr@gmail.com> [Wed, 22 Sep 2010 00:14:57 +0200] rev 12371
templater: add hex filter.
Tue, 21 Sep 2010 18:40:33 +0200 tests: unify test-convert-svn-*
Dan Villiom Podlaski Christiansen <danchr@gmail.com> [Tue, 21 Sep 2010 18:40:33 +0200] rev 12370
tests: unify test-convert-svn-*
Mon, 06 Sep 2010 17:35:49 +0200 merge: delay writing the mergestate during until commit is called
Peter Arrenbrecht <peter.arrenbrecht@gmail.com> [Mon, 06 Sep 2010 17:35:49 +0200] rev 12369
merge: delay writing the mergestate during until commit is called This speeds up merges of lots of files considerably.
(0) -10000 -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 +10000 +30000 tip