All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: "Carlo Marcelo Arenas Belón" <carenas@gmail.com>,
	"Stefan Haller" <lists@haller-berlin.de>,
	Git <git@vger.kernel.org>
Subject: Re: Would it make sense to add a commit.signOff config?
Date: Tue, 16 Dec 2025 10:20:04 +0900	[thread overview]
Message-ID: <xmqqike75ikb.fsf@gitster.g> (raw)
In-Reply-To: <aUCLz1wTOwilflAD@fruit.crustytoothpaste.net> (brian m. carlson's message of "Mon, 15 Dec 2025 22:29:35 +0000")

"brian m. carlson" <sandals@crustytoothpaste.net> writes:

> On 2025-12-15 at 01:59:46, Junio C Hamano wrote:
>> "brian m. carlson" <sandals@crustytoothpaste.net> writes:
>> 
>> > I think this would be a fine approach or we could add an entry in the
>> > Git FAQ (or both).  I agree that this is something that comes up
>> > frequently and writing it down in a more visible way would be kinder to
>> > users and mailing list participants.
>> 
>> Something like this, then?
>
> Yup, that looks good to me.

Thanks.

  reply	other threads:[~2025-12-16  1:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-14 16:10 Would it make sense to add a commit.signOff config? Stefan Haller
2025-12-14 16:44 ` Carlo Marcelo Arenas Belón
2025-12-14 23:44   ` Junio C Hamano
2025-12-14 23:52     ` Collin Funk
2025-12-15  1:22     ` brian m. carlson
2025-12-15  1:59       ` Junio C Hamano
2025-12-15 22:29         ` brian m. carlson
2025-12-16  1:20           ` Junio C Hamano [this message]
2025-12-16  0:17         ` Elijah Newren
2025-12-16  2:29           ` Junio C Hamano
2025-12-16  7:10             ` Johannes Sixt
2025-12-16  7:15           ` Johannes Sixt
2025-12-16 18:54         ` [PATCH v2] commit: document that $command.signoff will not be added Junio C Hamano
2025-12-16 19:48           ` Elijah Newren
2025-12-17  4:47             ` Junio C Hamano
2025-12-17  7:40               ` Elijah Newren
2025-12-17 13:51           ` Johannes Sixt
2025-12-17 23:16             ` Junio C Hamano
2025-12-19  7:33           ` Kristoffer Haugsbakk
2025-12-19 12:52             ` Junio C Hamano

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=xmqqike75ikb.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=carenas@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=lists@haller-berlin.de \
    --cc=sandals@crustytoothpaste.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.