Thu, 10 Sep 2009 01:56:25 +0200 transplant: Add trailing LF in tmp file for filtering
Mads Kiilerich <mads@kiilerich.com> [Thu, 10 Sep 2009 01:56:25 +0200] rev 9433
transplant: Add trailing LF in tmp file for filtering Transplant filtering used a tmp file ending with the (stripped) commit message and thus no final LF. Text files not ending with LF is usually not used on Unix and is thus wrong ;-) The missing LF had bad consequences because Solaris sed chokes on unterminated input lines, so echo -n foo|sed 's,o,0,g' doesn't output anything, and the filter used in tests/test-transplant thus stripped the last (and only) line in the message away on solaris.
Sun, 06 Sep 2009 15:32:16 +0200 Merge with crew-stable
Patrick Mezard <pmezard@gmail.com> [Sun, 06 Sep 2009 15:32:16 +0200] rev 9432
Merge with crew-stable
Sun, 06 Sep 2009 15:29:14 +0200 convert: fix history topology when using hg.tagsbranch
Patrick Mezard <pmezard@gmail.com> [Sun, 06 Sep 2009 15:29:14 +0200] rev 9431
convert: fix history topology when using hg.tagsbranch When using hg.tagsbranch, all conversions fail at transcribing the source repo topology with conversion scenarios interleaving: - initial repo conversion, - then upstream tag - then later incremental conversion The problem is caused by the usage of the last source revid as source revid for the tagnode in the revision map. On a later incremental conversion, when resolving some child commit of the true last source revid, convert will parent the nodes to the tag node. If using tagsbranch you get a bad topology where all incremental commit nodes end up in the tag branch. Analysis and test by Edouard Gomez <ed.gomez@free.fr>
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.
(0) -3000 -1000 -300 -100 -30 -10 -6 +6 +10 +30 +100 +300 +1000 +3000 +10000 +30000 tip