On Jun 16, 06 16:21:26 -0700, Junio C Hamano wrote: > Having said that, I would say it is a bug. We should be able to > rebase, cherry-pick and/or rebase a patch with an arbitrary > binary garbage in the commit log message (I think the latter two > command do). But because of the reason (2) above, it is very > low on my priority to change it. I understand. Many thanks for your explainations. I think this intended log format should be documented somewhere, that would help a lot. I don't think that many developers using git in CVS style know about this convention. Said that, I assume git nuking the multiline comment was a bug in 1.3.1 that has been (somewhat ;) solved. Matthias -- Matthias Hopf <mhopf@xxxxxxx> __ __ __ Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ mat@xxxxxxxxx Phone +49-911-74053-715 __) |_| __) |__ labs www.mshopf.de - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html