Sven Eckelmann sven@narfation.org schrieb am 26.02.2016 17:20:54:
See my other comments directly to the patches. Please try to set the in-reply-to of the patches to the message-id of the cover letter.
Otherwise
the messages aren't correctly threaded on the mailinglist [1].
Is there a way to generate the cover letter also with git send-email? As I did not know how to generate it, I used claws as a separate e-mail client.
And you can set the version number of the patch directly using git-format-patch:
git format-patch -v 2 origin/master
I haven't done the complete build_test run but at least a quick test
against
4.4 only. The result is attached.
Kind regards, Sven
I used checkpatch.pl of linux 4.5 rc5 and checked each patch seperately without open issues. These things with bracket alignment etc. start driving me crazy. Looks as if I don't use a proper editor. Can you recommend one to use before sending patches?
[1] https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2016-February/ thread.html [Anhang "build-test_andreas-pape_bla-fixes.mbox" gelöscht von Andreas Pape/Phoenix Contact] [Anhang "signature.asc" gelöscht von Andreas Pape/Phoenix Contact]
.................................................................. PHOENIX CONTACT ELECTRONICS GmbH
Sitz der Gesellschaft / registered office of the company: 31812 Bad Pyrmont USt-Id-Nr.: DE811742156 Amtsgericht Hannover HRB 100528 / district court Hannover HRB 100528 Geschäftsführer / Executive Board: Roland Bent, Dr. Martin Heubeck ___________________________________________________________________ Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren, jegliche anderweitige Verwendung sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. ---------------------------------------------------------------------------------------------------- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure, distribution or other use of the material or parts thereof is strictly forbidden. ___________________________________________________________________