From: Junio C Hamano <gitster@pobox.com>
To: Tuomas Ahola <taahol@utu.fi>
Cc: <git@vger.kernel.org>
Subject: Re: [PATCH] format-patch: use raw format for notes
Date: Tue, 18 Mar 2025 17:52:51 -0700 [thread overview]
Message-ID: <xmqq4izpzvrw.fsf@gitster.g> (raw)
In-Reply-To: <20250318.233012.1423505396684882738.taahol@utu.fi> (Tuomas Ahola's message of "Tue, 18 Mar 2025 23:30:12 +0200")
Tuomas Ahola <taahol@utu.fi> writes:
> From: Junio C Hamano <gitster@pobox.com>
> Subject: Re: [PATCH] format-patch: use raw format for notes
> Date: Tue, 18 Mar 2025 14:17:32 -0700
>
>> [--] more importantly, the contents of the note loses its crucial
>> leading spaces that makes sure that any random lines in the note
>> that happen to begin with "diff", "---", etc. are not mistaken as
>> the beginning of the first patch.
>
> Thanks for quick response. That was indeed a compelling point.
>
>> So, no, this change is not a good thing to do, at least in its
>> current form. Besides, unconditional change like this will break
>> existing users.
>
> I see that similar patch was proposed in 2017. I should have searched
> more thoroughly, I guess.
Heh, your archive spelunking skills are far superiour than mine, it
seems. And in
https://lore.kernel.org/git/xmqqingw8ppj.fsf@gitster.mtv.corp.google.com/
I see that I said exactly the same thing to exactly the same patch.
It is not to say that I've been a good person to be very consistent
(I do not have to be---over the years I can hear more opinions from
others that may sway how I think about the same issue), but says
that there aren't new arguments to sway the old decision in the past
7.5 years.
And exactly the same way as back then, I am open to a valid argument
to add such an output as an optional feature if there is a good use
case for it.
Thanks.
next prev parent reply other threads:[~2025-03-19 0:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 18:02 [PATCH] format-patch: use raw format for notes Tuomas Ahola
2025-03-18 21:14 ` brian m. carlson
2025-03-18 21:17 ` Junio C Hamano
2025-03-18 21:30 ` Tuomas Ahola
2025-03-19 0:52 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-08-28 4:23 Sam Bobroff
2017-09-06 3:34 ` Junio C Hamano
2017-09-11 4:27 ` Sam Bobroff
2017-09-12 17:33 ` Stefan Beller
2017-09-13 0:38 ` Sam Bobroff
2017-09-13 13:03 ` Jeff King
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=xmqq4izpzvrw.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=taahol@utu.fi \
/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).