Deal with failed clone/transaction interaction -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Deal with failed clone/transaction interaction > What is happening is that something in the transaction machinery is > causing the directory to be completely recreated. The transaction gets rolled back by its destructor. This is critical so it happens whenever an exception occurs that unwinds the stack. Unfortunately, what's happening with clone is we're trying to delete the directory during exception propagation. And a reference to the transaction is held in the exception backtrace stack frames so it still exists until the exception is completely resolved. So there's no way to do the directory delete inside the exception handling cleanly. But we can handle it similarly to the transaction itself: use an object with a destructor. manifest hash: fc38550a20d64d08333f256bbedc312493c1390b -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCxDT2ywK+sNU5EO8RAjikAJ0Tej56rAutxQDfYzVbFGtT1sEC5ACgmVds /fwdQyHn+FwshugqXLemUaM= =3f78 -----END PGP SIGNATURE-----

[PATCH] Handle 'name firstname <email@server>' correctly in annotate -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [PATCH] Handle 'name firstname <email@server>' correctly in annotate - From ed.gomez@free.fr manifest hash: 8af8d6b2afd8caf8e48e5150b91410dea730d41a -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCxCpzywK+sNU5EO8RAj8tAJ9lIXS7tlgonp6B810QahCZM0NsigCdH8xQ cRhEGvrKDrTgc4AY9guylDU= =+sWJ -----END PGP SIGNATURE-----

[PATCH] Generate correctly XML entities for obfuscated user -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [PATCH] Generate correctly XML entities for obfuscated user From: Edouard Gomez <ed.gomez@free.fr> manifest hash: 8e4e2d087ff60020c948d34e724fca99c84a9115 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCxCpDywK+sNU5EO8RAs6yAKCy97yrMO6VYlkRIF3diLoGClZSOgCfekPE ttPsLRoDTH12Tv6omFg6uUA= =8ZBC -----END PGP SIGNATURE-----