Git Mailing List Archive mirror
 help / color / mirror / Atom feed
From: Brian Inglis <>
Subject: manual option --inline --no-attach override required for format.attach
Date: Wed, 15 Feb 2023 14:51:13 -0700	[thread overview]
Message-ID: <> (raw)

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

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]

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-15 21:51 Brian Inglis [this message]
2023-02-15 22:21 ` manual option --inline --no-attach override required for format.attach Junio C Hamano
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 \ \ \ \

* 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).