Fri, 02 Jul 2010 15:05:21 +0900 hg.clone: fix branch value when passing a repo object (issue2267) stable
Nicolas Dumazet <nicdumz.commits@gmail.com> [Fri, 02 Jul 2010 15:05:21 +0900] rev 11544
hg.clone: fix branch value when passing a repo object (issue2267) Since 3d6915f5a2bb the branch argument for addbranchrevs should be a tuple: (hashbranch, branches) The right empty value therefore is (None, []) instead of None.
Tue, 06 Jul 2010 15:05:03 +0900 test-bheads: use a case-insensitive set of filenames (issue2274) stable
Nicolas Dumazet <nicdumz.commits@gmail.com> [Tue, 06 Jul 2010 15:05:03 +0900] rev 11543
test-bheads: use a case-insensitive set of filenames (issue2274) This prevents false negatives on case-insensitive systems.
Tue, 06 Jul 2010 18:24:04 +0900 mail: ensure that Python2.4 to 2.7 use the same header format stable
Nicolas Dumazet <nicdumz.commits@gmail.com> [Tue, 06 Jul 2010 18:24:04 +0900] rev 11542
mail: ensure that Python2.4 to 2.7 use the same header format Wrapping format for long headers changed in Python2.7 (see Python issue1974). Adopt the Python2.7 behaviour and backport it for 2.4-2.6
Mon, 05 Jul 2010 19:49:54 +0900 filelog: cmp: don't read data if hashes are identical (issue2273) stable
Nicolas Dumazet <nicdumz.commits@gmail.com> [Mon, 05 Jul 2010 19:49:54 +0900] rev 11541
filelog: cmp: don't read data if hashes are identical (issue2273) filelog.renamed() is an expensive call as it reads the filelog if p1 == nullid. It's more efficient to first compute the hash, and to bail early if the computed hash is the same as the stored nodeid. 'samehashes' variable is not strictly necessary, but helps for comprehension.
Mon, 05 Jul 2010 18:43:46 +0900 filelog: test behaviour for data starting with "\1\n" stable
Nicolas Dumazet <nicdumz.commits@gmail.com> [Mon, 05 Jul 2010 18:43:46 +0900] rev 11540
filelog: test behaviour for data starting with "\1\n" Because "\1\n" is a separator for metadata, data starting with "\1\n" is handled specifically. It was not tested. size() call return incorrect data if original data had been "\1\n-escaped". There's no obvious way to fix it for now, just flag the error in the code and add an "expected failure" kind of test.
Fri, 09 Jul 2010 11:02:39 +0900 cmp: document the fact that we return True if content is different stable
Nicolas Dumazet <nicdumz.commits@gmail.com> [Fri, 09 Jul 2010 11:02:39 +0900] rev 11539
cmp: document the fact that we return True if content is different This is similar to the __builtin__.cmp behaviour, but still not straightforward, as the dailylife meaning of a comparison usually is "find out if they are different".
Fri, 09 Jul 2010 11:59:48 +0900 workingfilectx.cmp: invert boolean return value stable
Nicolas Dumazet <nicdumz.commits@gmail.com> [Fri, 09 Jul 2010 11:59:48 +0900] rev 11538
workingfilectx.cmp: invert boolean return value Apparently we mostly used filectx.cmp(workingfilectx.read()), so no error was ever triggered, but since all cmp() methods return True when content are different, that == should in fact be !=
Mon, 12 Jul 2010 19:04:07 +0900 rebase: small cosmetic cleanups stable
Nicolas Dumazet <nicdumz.commits@gmail.com> [Mon, 12 Jul 2010 19:04:07 +0900] rev 11537
rebase: small cosmetic cleanups
Mon, 12 Jul 2010 09:19:28 +0300 rebase: add a test for committed MQ patches (59bd20451ab6) stable
Giorgos Keramidas <keramida@ceid.upatras.gr> [Mon, 12 Jul 2010 09:19:28 +0300] rev 11536
rebase: add a test for committed MQ patches (59bd20451ab6)
Fri, 02 Jul 2010 16:21:40 -0300 util.h: Defined macros for working "with" PyStrings in py3k.
Renato Cunha <renatoc@gmail.com> [Fri, 02 Jul 2010 16:21:40 -0300] rev 11535
util.h: Defined macros for working "with" PyStrings in py3k. PyString* functions are defined as PyUnicode* to permit correct compilation in both python 2.x and 3.x.
(0) -10000 -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 +10000 +30000 tip