Git Mailing List Archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <>
To: Brian Inglis <>
Subject: Re: manual option --inline --no-attach override required for format.attach
Date: Wed, 15 Feb 2023 14:21:58 -0800	[thread overview]
Message-ID: <xmqqr0uqwovt.fsf@gitster.g> (raw)
In-Reply-To: <> (Brian Inglis's message of "Wed, 15 Feb 2023 14:51:13 -0700")

Brian Inglis <> writes:

> What did you do before the bug happened? (Steps to reproduce your issue)
> git format-patch --inline ...

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

> git format-patch --no-attach ...

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

> git send-email ...

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.

  reply	other threads:[~2023-02-15 22:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-15 21:51 manual option --inline --no-attach override required for format.attach Brian Inglis
2023-02-15 22:21 ` Junio C Hamano [this message]
2023-02-17 22:12   ` Brian Inglis
2023-02-16  1:29 ` manual option --inline --no-attach override required for format.attachg brian m. carlson

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqr0uqwovt.fsf@gitster.g \ \ \ \

* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).