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

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

From
BIBrian Inglis <brian.inglis@shaw.ca>
Date
Feb 15, 2023, 21:51 UTC
Message-ID
<20230215215112.62559-1-Brian.Inglis@Shaw.ca>

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

What did you expect to happen? (Expected behavior) linux-man maintainer would get patches inline not in attachments as expected

What happened instead? (Actual behavior) linux-man maintainer got patches in MIME attachments which he could not use

What's different between what you expected and what actually happened? using format-patch either --inline or --no-attach would send patches inline need to remember to specify format-patch --inline --no-attach for every patch there is no way to set config format.inline format.attach=no

Anything else you want to add: initially found format.attach set in /etc/gitconfig and no way to override would be great if linux-man maintainer could set repo config format.inline format.attach=no

[System Info] git version: git version 2.39.0 cpu: x86_64 no commit associated with this build sizeof-long: 8 sizeof-size_t: 8 shell-path: /bin/sh uname: CYGWIN_NT-10.0-19044 3.4.6-1.x86_64 2023-02-14 13:23 UTC x86_64 compiler info: gnuc: 11.3 libc info: newlib 4.3.0 $SHELL (typically, interactive shell): /bin/bash

[Enabled Hooks]
Next: Junio C Hamano
Message 1 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.