Matt Mackall <mpm@selenic.com> [Mon, 01 Feb 2010 09:18:25 -0600] rev 10308
Merge with i18n
Wagner Bruna <wbruna@softwareexpress.com.br> [Mon, 01 Feb 2010 11:11:30 -0200] rev 10307
merge with i18n stable
Wagner Bruna <wbruna@softwareexpress.com.br> [Mon, 01 Feb 2010 11:10:43 -0200] rev 10306
i18n-pt_BR: synchronized with b08ffd27dfc8
Martin Geisler <mg@lazybytes.net> [Sun, 31 Jan 2010 16:01:20 +0100] rev 10305
Merge with stable.
Georg Brandl <georg@python.org> [Sat, 30 Jan 2010 19:49:52 +0100] rev 10304
i18n: fix typo in German translation
FUJIWARA Katsunori <foozy@lares.dti.ne.jp> [Sun, 31 Jan 2010 02:34:50 +0900] rev 10303
i18n-ja: synchronized with e7727a545c48
Matt Mackall <mpm@selenic.com> [Sun, 31 Jan 2010 13:43:33 -0600] rev 10302
Merge with stable
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.
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
Benoit Boissinot <benoit.boissinot@ens-lyon.org> [Sun, 31 Jan 2010 18:02:16 +0100] rev 10299
subrepo: fix errors reported by pylint