From: Matthieu Baerts <matttbe@kernel.org>
To: Quentin Schulz <quentin.schulz@cherry.de>,
"Kernel.org Tools" <tools@kernel.org>
Cc: Farouk Bouabid <farouk.bouabid@cherry.de>
Subject: Re: [b4] add notes to patch for commit with git-notes?
Date: Mon, 2 Sep 2024 19:10:16 +0200 [thread overview]
Message-ID: <c3ee39c3-afae-4918-a82d-148cf62c93af@kernel.org> (raw)
In-Reply-To: <4bc5dee0-ed3a-442c-a9ee-d48050627576@cherry.de>
Hi Quentin,
On 02/09/2024 18:51, Quentin Schulz wrote:
> I think it should be possible to use git-notes for the latter?
Please note :) that these notes can be easily dropped by b4 itself when
editing commits because it uses 'git filter-repo' to do so [1]. In other
words, these notes will be dropped when using 'b4 trailers', or when
using some 'b4 prep' commands when the cover-letter is stored in a
dedicated commit.
> The diff we had for b4 to make this work is the following:
The diff you attached has already proposed before in [2], but not
applied because the notes can be dropped.
> Let me know if git-notes would be fine and the direction to go for
> patches. Thanks!
Unfortunately, I don't think that's the right direction. The alternative
is to add the notes in the commit message, at the end, under '---' [3].
Maybe the direction to take is to document this alternative :)
[1]
https://lore.kernel.org/tools/20220929074717.u2xfvfwq4ki732tw@wittgenstein/T/
[2]
https://lore.kernel.org/tools/20240131223054.371692-1-Frank.Li@nxp.com/T/
[3]
https://lore.kernel.org/tools/jx7vyqdj3qt2zwgsxh6hjac6osr52n2vcmkj2pg3elapcth62m@jtl27si2pa3g/
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2024-09-02 17:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 16:51 [b4] add notes to patch for commit with git-notes? Quentin Schulz
2024-09-02 17:10 ` Matthieu Baerts [this message]
2024-09-02 17:19 ` Quentin Schulz
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=c3ee39c3-afae-4918-a82d-148cf62c93af@kernel.org \
--to=matttbe@kernel.org \
--cc=farouk.bouabid@cherry.de \
--cc=quentin.schulz@cherry.de \
--cc=tools@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