From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Yazen Ghannam <yazen.ghannam@amd.com>
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:29:09 -0500 [thread overview]
Message-ID: <20250130-powerful-versed-carp-ce8ecc@lemur> (raw)
In-Reply-To: <20250130210453.GA615204@yaz-khff2.amd.com>
On Thu, Jan 30, 2025 at 04:04:53PM -0500, Yazen Ghannam wrote:
> > 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.
Unfortunately, tip-commit is not going to fix all instances where this is
likely to break. E.g. running 'b4 trailers -u' will also rebase your series
and lose your notes.
> Could we document some tips for this topic? Or just leave it for now?
I'd just leave it for now. Hopefully, we'll eventually get to the point where
notes are supported without any workarounds (though I've been waiting for a
few years now).
-K
prev parent reply other threads:[~2025-01-30 21:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 20:13 [PATCH] b4: Include git notes when generating patches Yazen Ghannam
2025-01-30 20:30 ` Konstantin Ryabitsev
2025-01-30 21:04 ` Yazen Ghannam
2025-01-30 21:29 ` Konstantin Ryabitsev [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=20250130-powerful-versed-carp-ce8ecc@lemur \
--to=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tools@kernel.org \
--cc=yazen.ghannam@amd.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;
as well as URLs for NNTP newsgroup(s).