Re: Git send-email not sending email patches as subsequent replies

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



David Davis <davidjamesdavis.djd@xxxxxxxxx> wrote:
> Hello, I have the following git send-email command:
> 
> git send-email -5 --quiet --thread --no-chain-reply-to --compose
> --subject='Recent Base Prototype Changes Summary'
> --to=davisdavid@xxxxxxxxxx --from=davisdavid@xxxxxxxxxx
> 
> It's sending emails but as 5 individual emails and not as subsequent
> replies as suggested on https://git-scm.com/docs/git-send-email below:

So, I expect the above command should give you six emails:

  [PATCH 0/5] Recent Base Prototype Changes Summary
    [PATCH 1/5]
    [PATCH 2/5]
    [PATCH 3/5]
    [PATCH 4/5]
    [PATCH 5/5]

Is that not what you're seeing?

You're quoting the manpage for --in-reply-to option below,
but you're not using that option.

> So for example when --thread and --no-chain-reply-to are specified,
> the second and subsequent patches will be replies to the first one
> like in the illustration below where [PATCH v2 0/3] is in reply to
> [PATCH 0/2]:
> 
> [PATCH 0/2] Here is what I did...
>   [PATCH 1/2] Clean up and tests
>   [PATCH 2/2] Implementation
>   [PATCH v2 0/3] Here is a reroll
>     [PATCH v2 1/3] Clean up
>     [PATCH v2 2/3] New tests
>     [PATCH v2 3/3] Implementation
> 
> What am I missing?

I'm not sure...  I suspect you're either not using --in-reply-to=
or misreading the manpage, somehow.



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux