From: Yazen Ghannam <yazen.ghannam@amd.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] b4: Include git notes when generating patches
Date: Thu, 30 Jan 2025 16:04:53 -0500 [thread overview]
Message-ID: <20250130210453.GA615204@yaz-khff2.amd.com> (raw)
In-Reply-To: <20250130-rich-orangutan-from-eldorado-04f621@lemur>
On Thu, Jan 30, 2025 at 03:30:59PM -0500, Konstantin Ryabitsev wrote:
> On Thu, Jan 30, 2025 at 08:13:31PM +0000, Yazen Ghannam wrote:
> > By default, 'git show' will include git notes in its output. However,
> > this is not the case if '--format', or related flags, are given.
> >
> > Include the '--notes' flag to include git notes in the generated patch.
>
> I'd love to do that, but git-filter-repo currently doesn't do the right thing
> with notes, so anyone who starts to rely on notes will find that they are
> easily lost with most common b4 operations. There's a long-standing RFE to
> support notes with git-filter-repo:
>
> https://github.com/newren/git-filter-repo/issues/22
>
> Until that happens, I really don't want to pretend that we support notes,
> because this will result in bad experiences for most who try it.
>
Right, I've encountered issues myself. I've found that the 'tip-commit'
cover letter strategy works, since git-filter-repo will only operate on
the final commit.
Could we document some tips for this topic? Or just leave it for now?
Thanks,
Yazen
next prev parent reply other threads:[~2025-01-30 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 20:13 Yazen Ghannam
2025-01-30 20:30 ` Konstantin Ryabitsev
2025-01-30 21:04 ` Yazen Ghannam [this message]
2025-01-30 21:29 ` Konstantin Ryabitsev
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=20250130210453.GA615204@yaz-khff2.amd.com \
--to=yazen.ghannam@amd.com \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®