git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: git@vger.kernel.org,  Patrick Steinhardt <ps@pks.im>,
	 Elijah Newren <newren@gmail.com>,  Jeff King <peff@peff.net>,
	 "brian m . carlson" <sandals@crustytoothpaste.net>,
	 Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	 Christian Couder <chriscool@tuxfamily.org>
Subject: Re: [PATCH 2/2] fast-import: add '--signed-commits=<mode>' option
Date: Fri, 12 Sep 2025 07:14:47 -0700	[thread overview]
Message-ID: <xmqqa52zoizs.fsf@gitster.g> (raw)
In-Reply-To: <CAP8UFD0EAuGdMWY2ff_kjaQnZ3w7VP2ftM6Y4Hr3T4HQTsFB3w@mail.gmail.com> (Christian Couder's message of "Fri, 12 Sep 2025 15:35:45 +0200")

Christian Couder <christian.couder@gmail.com> writes:

>> ...  Was it so important that we pass a
>> broken signature without inspecting in STRIP mode?  I am guessing
>> that is the reason why the new code tries hard to avoid calling the
>> parse_one_signature() function in these case arms.
>
> Yeah, I thought it was cleaner and a bit faster if we don't parse
> signatures when in STRIP mode. That's why I did it like this.

I do not think parsing performance matters all that much here, but I
think it is a good idea to recover from malformed signature lines if
the parsing code can detect some.  It is likely that the user may be
using STRIP hoping that they can skip bad or unknown signature data
in the incoming stream, so it is beneficial to be lenient there.

> Now as it looks like we don't really mind parsing them, I implemented
> that in V2. In ABORT mode, I still think it might be a bit better to
> ABORT right away though, so that's what I implemented in V2.
>
>> An aside.  I think the warning message about importing should have a
>> word "verbatim" in it, e.g.
>>
>>         warning("importing a commit signature verbatim");
>
> In V2, I have changed the message to what you suggest.

Sounds good.

Thanks.

  reply	other threads:[~2025-09-12 14:14 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-10  8:08 [PATCH 0/2] fast-import: start controlling how commit signatures are handled Christian Couder
2025-09-10  8:08 ` [PATCH 1/2] gpg-interface: refactor 'enum sign_mode' parsing Christian Couder
2025-09-10 16:50   ` Junio C Hamano
2025-09-11  6:06   ` Patrick Steinhardt
2025-09-11 16:29     ` Junio C Hamano
2025-09-12 12:40       ` Christian Couder
2025-09-12 12:40     ` Christian Couder
2025-09-10  8:08 ` [PATCH 2/2] fast-import: add '--signed-commits=<mode>' option Christian Couder
2025-09-10 17:09   ` Junio C Hamano
2025-09-12 13:35     ` Christian Couder
2025-09-12 14:14       ` Junio C Hamano [this message]
2025-09-15 10:29         ` Christian Couder
2025-09-15 16:02           ` Junio C Hamano
2025-09-17 18:27             ` Christian Couder
2025-09-10 18:21   ` Junio C Hamano
2025-09-12 13:41     ` Christian Couder
2025-09-12 14:09       ` Junio C Hamano
2025-09-11  6:06   ` Patrick Steinhardt
2025-09-11 16:55     ` Junio C Hamano
2025-09-12 13:47       ` Christian Couder
2025-09-12 13:25     ` Christian Couder

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=xmqqa52zoizs.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=chriscool@tuxfamily.org \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=newren@gmail.com \
    --cc=peff@peff.net \
    --cc=ps@pks.im \
    --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 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 NNTP newsgroup(s).