From: Eric Wong <e@80x24.org>
To: David Davis <davidjamesdavis.djd@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Git send-email not sending email patches as subsequent replies
Date: Sat, 7 Apr 2018 23:08:48 +0000 [thread overview]
Message-ID: <20180407230848.GA5048@80x24.org> (raw)
In-Reply-To: <CANqAOmsZxpbkT3YFcZTOeRx2gnxnzc+_C-amVQjKSE=0m7_n7w@mail.gmail.com>
David Davis <davidjamesdavis.djd@gmail.com> 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@google.com --from=davisdavid@google.com
>
> 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.
next prev parent reply other threads:[~2018-04-07 23:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 19:28 Git send-email not sending email patches as subsequent replies David Davis
2018-04-07 23:08 ` Eric Wong [this message]
[not found] ` <CANqAOmvjiiBQs4GHrFbBBXygwVEsCkH7ceSsFKFpmvscKCWrGg@mail.gmail.com>
2018-04-08 2:47 ` Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180407230848.GA5048@80x24.org \
--to=e@80x24.org \
--cc=davidjamesdavis.djd@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.