From: "Kristoffer Haugsbakk" <code@khaugsbakk.name>
To: "Junio C Hamano" <gitster@pobox.com>, "David Disseldorp" <ddiss@suse.de>
Cc: git@vger.kernel.org, "Teng Long" <dyroneteng@gmail.com>
Subject: Re: [PATCH 2/2] notes: revert note_data.given behavior with empty notes add
Date: Thu, 25 Jul 2024 19:22:39 +0200 [thread overview]
Message-ID: <ae5dc48b-07df-45ab-a3b7-4d5c27fdbfa2@app.fastmail.com> (raw)
In-Reply-To: <xmqqzfq5flfd.fsf@gitster.g>
On Thu, Jul 25, 2024, at 19:09, Junio C Hamano wrote:
>> Fixes: 90bc19b3ae ("notes.c: introduce '--separator=<paragraph-break>' option")
>> Link: https://github.com/ddiss/icyci/issues/12
>
> We generally refrain from using these two trailers. Please drop them.
>
> Especially "Fixes" claim can later prove incorrect (we thought this
> was a good fix when committing, but it later turned out to be a bad
> one), and besides you will be referring to the problematic commit in
> your proposed log message already anyway.
David, if you want to mention your downstream issue you can use a
“footnote” in the commit message:
With "git notes add -C $blob", the given blob contents are
to be made into a note without involving an editor. But
when "--allow-empty" is given, the editor is invoked.[1]
<rest of the commit message>
[1] https://github.com/ddiss/icyci/issues/12
Signed-off-by: …
This is widely practiced.
--
Kristoffer Haugsbakk
next prev parent reply other threads:[~2024-07-25 17:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 14:41 [PATCH 0/2] notes: fix editor invocation regression David Disseldorp
2024-07-25 14:41 ` [PATCH 1/2] t3301-notes: check editor isn't invoked for empty notes add David Disseldorp
2024-07-25 15:52 ` Kristoffer Haugsbakk
2024-07-25 16:03 ` David Disseldorp
2024-07-25 17:10 ` Junio C Hamano
2024-07-25 16:31 ` Junio C Hamano
2024-07-25 23:10 ` David Disseldorp
2024-07-25 14:41 ` [PATCH 2/2] notes: revert note_data.given behavior with " David Disseldorp
2024-07-25 17:09 ` Junio C Hamano
2024-07-25 17:22 ` Kristoffer Haugsbakk [this message]
2024-07-25 23:26 ` David Disseldorp
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=ae5dc48b-07df-45ab-a3b7-4d5c27fdbfa2@app.fastmail.com \
--to=code@khaugsbakk.name \
--cc=ddiss@suse.de \
--cc=dyroneteng@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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