Sun, 31 Jan 2010 16:01:20 +0100 Merge with stable.
Martin Geisler <mg@lazybytes.net> [Sun, 31 Jan 2010 16:01:20 +0100] rev 10305
Merge with stable.
Sat, 30 Jan 2010 19:49:52 +0100 i18n: fix typo in German translation stable
Georg Brandl <georg@python.org> [Sat, 30 Jan 2010 19:49:52 +0100] rev 10304
i18n: fix typo in German translation
Sun, 31 Jan 2010 02:34:50 +0900 i18n-ja: synchronized with e7727a545c48
FUJIWARA Katsunori <foozy@lares.dti.ne.jp> [Sun, 31 Jan 2010 02:34:50 +0900] rev 10303
i18n-ja: synchronized with e7727a545c48
Sun, 31 Jan 2010 13:43:33 -0600 Merge with stable
Matt Mackall <mpm@selenic.com> [Sun, 31 Jan 2010 13:43:33 -0600] rev 10302
Merge with stable
Sun, 24 Jan 2010 20:51:53 +0100 templates: rename `Last change' column in hgwebdir repository list.
Dan Villiom Podlaski Christiansen <danchr@gmail.com> [Sun, 24 Jan 2010 20:51:53 +0100] rev 10301
templates: rename `Last change' column in hgwebdir repository list. This patch changes column headers in the templates that previously said `Last change' to `Last modified'. Neither code nor functionality are changed other than that. For some time now, I have been annoyed by the fact the `Last change' column didn't list the age of the youngest changeset in the repository, or at least tip. It just occurred to me that this is because the wording is slightly misleading; what the column in fact lists is when the repository was last *modified*, that is, when changesets was last added or removed from it. The word `change' can be understood as referring to the changeset itself. Using `changed' would be ever so slightly less amigous. However, the standard nomenclature in this case is `modification date' and `Last modified', which is incidentally entirely unambigous. Hence, `Last modified' is the wording used.
Thu, 10 Dec 2009 17:21:31 +0900 run-tests: split tests/blacklist in tests/blacklists/*
Nicolas Dumazet <nicdumz.commits@gmail.com> [Thu, 10 Dec 2009 17:21:31 +0900] rev 10300
run-tests: split tests/blacklist in tests/blacklists/* Following discussions with Gilles Morris [1], it seems that it is preferable to use several blacklist files in a blacklists/ directory. It is easier to add an unversioned file for experiments than modifying a tracked file. Also fall back to a simpler syntax, giving up ConfigParser, now that section names are not needed anymore. And allow --blacklist parameter to be a complete path, instead of only one of the filenames contained in tests/blacklists/ [1] http://www.selenic.com/pipermail/mercurial-devel/2009-December/017317.html
(0) -10000 -3000 -1000 -300 -100 -30 -10 -6 +6 +10 +30 +100 +300 +1000 +3000 +10000 +30000 tip