From: Jeff King <peff@peff.net>
To: Michael J Gruber <git@grubix.eu>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] notes: avoid empty line in template
Date: Thu, 17 Nov 2022 10:12:27 -0500 [thread overview]
Message-ID: <Y3ZPW/seP0auAtKZ@coredump.intra.peff.net> (raw)
In-Reply-To: <166867999215.10813.7408480606700051633.git@grubix.eu>
On Thu, Nov 17, 2022 at 11:13:12AM +0100, Michael J Gruber wrote:
> > I don't mind the consistency here, but what does "wrong structurally"
> > mean? Doesn't the usual removing of duplicate newlines make this amount
> > to the same?
>
> I am talking about what we present to the user as a template, and that
> contains two newlines. Whether they will be reduced afterwards depends
> on the cleanup policy.
I wondered if this might actually be a non-cosmetic bug, if you could so
something like:
git notes add --cleanup=only-comments
which would retain the extra newlines. But there is no --cleanup option
for git-notes at all (it always calls strbuf_stripspace() internally).
And there is no "comments only" cleanup mode; it is either "clean
nothing", "clean space but leave comments", or "clean both".
So I think it really is just cosmetic.
-Peff
prev parent reply other threads:[~2022-11-17 15:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 15:56 [PATCH] notes: avoid empty line in template Michael J Gruber
2022-11-16 18:52 ` Jeff King
2022-11-16 19:57 ` Taylor Blau
2022-11-17 9:48 ` Ævar Arnfjörð Bjarmason
2022-11-17 10:13 ` Michael J Gruber
2022-11-17 15:12 ` Jeff King [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:
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=Y3ZPW/seP0auAtKZ@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=avarab@gmail.com \
--cc=git@grubix.eu \
--cc=git@vger.kernel.org \
/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