git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: manual option --inline --no-attach override required for format.attach

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 15, 2023, 22:21 UTC
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.

Previous: Brian InglisNext: Brian Inglis
Message 2 of 4 in “manual option --inline --no-attach override required for format.attach”
  1. Brian InglisFeb 15, 2023
  2. Junio C HamanoFeb 15, 2023
  3. Brian InglisFeb 17, 2023
  4. brian m. carlsonFeb 16, 2023

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.