How to use git-send-email for deep threading

[Silvan Jegen]

Am 2015-01-19 09:20, schrieb Sunil Shahu:
> Two Solution Files (Makefile and .c driver file)
>     └─> [PATCH 01/02] Patch 1 on earlier solution file
>         └─> [PATCH 02/02] Patch 2 on earlier solution file
> 
> I tired using different options in git send-email, but what I get is
> incorrect linking of mails.
> Two Solution Files (Makefile and .c driver file)
> [PATCH 01/02] Patch 1 on earlier solution file
>      └─> [PATCH 02/02] Patch 2 on earlier solution file
> I am not able to send two files using git send-email for the first
> email. I have to use --force to send any source file. Even in this,
> only first file is attached in mail.

You should not attach patches to your mails but send them inline.


> I also tried send first file using web browser mail client and then
> sending patches using git send-email, but it also do not work as
> expected.
> I have read git-send-email documentation but not able to comprehend
> how I can achieve my requirement from it. Can someone please give
> pointers on how I can send email correctly as per my requirement using
> git-send-email?

In general, you should be using git format-patch to prepare your patches 
to be sent by git send-email. The git-format-patch(1) man page should be 
helpful.


Cheers,

Silvan