Git Mailing List Archive mirror
 help / color / mirror / Atom feed
From: "brian m. carlson" <>
To: unlisted-recipients:; (no To-header on input)
Subject: Re: manual option --inline --no-attach override required for format.attachg
Date: Thu, 16 Feb 2023 01:29:45 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1085 bytes --]

On 2023-02-15 at 21:51:13, Brian Inglis wrote:
> 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

I think Junio has responded to the rest of this and is more familiar
with it than I am, but we don't allow repository configuration to be
shipped in the repo.  That's because in general configuration can
contain programs or shell commands and thus execute arbitrary code, so
doing so would be a security problem.

Experiences with Vim modelines have shown that embedding configuration,
even when highly restricted, can be the cause of lots of security
vulnerabilities, and we've seen this with config used by submodules in
the past.  For that and many other reasons, including the fact that
users may not care what upstream's preferred settings are, it's
extremely unlikely that we'll add any automatic way to ship
configuration in the repository.
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

      parent reply	other threads:[~2023-02-16  1:29 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
2023-02-17 22:12   ` Brian Inglis
2023-02-16  1:29 ` brian m. carlson [this message]

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