From: Junio C Hamano <gitster@pobox.com>
Date: Wed, 15 Feb 2023 22:21:58 GMT
Subject: Re: manual option --inline --no-attach override required for format.attach
Message-ID: <xmqqr0uqwovt.fsf@gitster.g>
In-Reply-To: <20230215215112.62559-1-Brian.Inglis@Shaw.ca>

Brian Inglis <Brian.Inglis@Shaw.ca> writes:

> What did you do before the bug happened? (Steps to reproduce your issue)
> git format-patch --inline ... --to=linux-man@vger.kernel.org

This is documented to use multipart/mixed attachement with
"Content-Disposition: inline".

> git format-patch --no-attach ... --to=linux-man@vger.kernel.org

This should be the default, text/plain patch contained inline in the
message.

> git send-email ... --to=linux-man@vger.kernel.org

It is unclera what ... hides on this command line, but if you sent
output from both of the above two format-patch invocations, then the
output from the first invocation of format-patch with --inline would
be MIME multipart messages, so it is understandable if the recipient
sees such messages.