Sat, 05 Sep 2009 19:39:46 +0200 Merge with crew-stable
Patrick Mezard <pmezard@gmail.com> [Sat, 05 Sep 2009 19:39:46 +0200] rev 9430
Merge with crew-stable
Sat, 05 Sep 2009 18:56:51 +0200 merge: exclude common ancestor from --preview (issue1818)
Patrick Mezard <pmezard@gmail.com> [Sat, 05 Sep 2009 18:56:51 +0200] rev 9429
merge: exclude common ancestor from --preview (issue1818)
Thu, 27 Aug 2009 11:55:21 +0200 inotify: _inotify.c: bugfix: remove_watch has to return PyNone on success
Nicolas Dumazet <nicdumz.commits@gmail.com> [Thu, 27 Aug 2009 11:55:21 +0200] rev 9428
inotify: _inotify.c: bugfix: remove_watch has to return PyNone on success We are not currently using that API function in inotify, hence the reason for the "silent" bug. But returning NULL here causes the interpreter to crash. Let's keep code clean for reusers :) The whole "bail" logic was unneeded here.
Thu, 27 Aug 2009 14:15:04 +0200 parsers.c: parse_manifest: fixing refcount of flags
Nicolas Dumazet <nicdumz.commits@gmail.com> [Thu, 27 Aug 2009 14:15:04 +0200] rev 9427
parsers.c: parse_manifest: fixing refcount of flags When flags was DECREF'ed, scope was referencing to the outer variable, outside of the block. It was in fact always NULL: the real Python object was never decref'ed.
Fri, 04 Sep 2009 23:45:13 +0200 test-highlight: remove redundant test
Martin Geisler <mg@lazybytes.net> [Fri, 04 Sep 2009 23:45:13 +0200] rev 9426
test-highlight: remove redundant test Changeset 799373ff2554 is testing how a EUC-JP encoded Japanese file is treated in different encodings, so the ISO-8859-1 encoded German file is no longer needed.
Fri, 04 Sep 2009 23:34:51 +0200 Merge with crew-stable
Martin Geisler <mg@lazybytes.net> [Fri, 04 Sep 2009 23:34:51 +0200] rev 9425
Merge with crew-stable
Sat, 29 Aug 2009 15:24:15 +0900 highlight: fixes garbled text in non-UTF-8 environment
Yuya Nishihara <yuya@tcha.org> [Sat, 29 Aug 2009 15:24:15 +0900] rev 9424
highlight: fixes garbled text in non-UTF-8 environment This patch treats all files inside repository as encoded by locale's encoding when pygmentize. We can assume that most files are written in locale's encoding, but current implementation treats them as UTF-8. So there's no way to specify the encoding of files. Current implementation, db7557359636 (issue1341): 1. Convert original `text`, which is treated as UTF-8, to locale's encoding. `encoding.tolocal()` is the method to convert from internal UTF-8 to local. If original `text` is not UTF-8, e.g. Japanese EUC-JP, some characters become garbled here. 2. pygmentize, with no UnicodeDecodeError. This patch: 1. Convert original `text`, which is treated as locale's encoding, to unicode. Pygments prefers unicode object than raw str. [1]_ If original `text` is not encoded by locale's encoding, some characters become garbled here. 2. pygmentize, also with no UnicodeDecodeError :) 3. Convert unicode back to raw str, which is encoded by locale's. .. [1] http://pygments.org/docs/unicode/
Mon, 31 Aug 2009 10:58:33 -0500 Make distinct lookup error for localrepo.lookup
Matt Mackall <mpm@selenic.com> [Mon, 31 Aug 2009 10:58:33 -0500] rev 9423
Make distinct lookup error for localrepo.lookup This allows clone/share to correctly distinguish lookup errors from corruption errors and catch only the former.
Fri, 04 Sep 2009 22:26:57 +0200 doc: add TOC to hg.1.html and hgrc.5.html
Martin Geisler <mg@lazybytes.net> [Fri, 04 Sep 2009 22:26:57 +0200] rev 9422
doc: add TOC to hg.1.html and hgrc.5.html
Fri, 04 Sep 2009 11:51:28 +0200 log: prevent negative date range from displaying entire log (issue1805)
Christian Ebert <blacktrash@gmx.net> [Fri, 04 Sep 2009 11:51:28 +0200] rev 9421
log: prevent negative date range from displaying entire log (issue1805)
(0) -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 +10000 +30000 tip