From: Mark Brown <broonie@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Maxime Ripard <maxime@cerno.tech>,
users@linux.kernel.org, tools@linux.kernel.org
Subject: Re: b4 bugs / future improvements
Date: Tue, 18 Oct 2022 21:29:44 +0100 [thread overview]
Message-ID: <Y08MuItOLxqpBr+/@sirena.org.uk> (raw)
In-Reply-To: <20221018201804.na5x7lohm4yszg5h@nitro.local>
[-- Attachment #1: Type: text/plain, Size: 903 bytes --]
On Tue, Oct 18, 2022 at 04:18:04PM -0400, Konstantin Ryabitsev wrote:
> On Tue, Oct 18, 2022 at 05:36:20PM +0200, Maxime Ripard wrote:
> > - Generally speaking, rebasing a b4 series is a bit troublesome:
> >
> > - It's a bit tedious to do. One needs to rebase and then edit the
> > cover letter by hand without b4 being involved. I don't think doing
> > the rebase interface all over again is reasonable, but maybe we
> > could add a subcommand to set a new base?
> Interesting. I'm not sure I fully understand the problem, but then all my
> rebase tests were all very simple cases of running "git rebase <newtag>"
> Is there a reason why you have to manually edit the cover letter after a
> rebase?
If you're doing an inter-version changelog it's common to say something
like "rebased against foo" in there. It's a bit clearer about things
than base-commit.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-10-18 20:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 15:36 b4 bugs / future improvements Maxime Ripard
2022-10-18 20:18 ` Konstantin Ryabitsev
2022-10-18 20:29 ` Mark Brown [this message]
2022-10-18 20:37 ` Konstantin Ryabitsev
2022-10-19 8:04 ` Maxime Ripard
2022-10-19 19:16 ` Konstantin Ryabitsev
2022-10-20 8:41 ` Maxime Ripard
2022-10-19 2:05 ` Rob Herring
2022-10-19 8:01 ` Maxime Ripard
2022-10-19 19:21 ` Konstantin Ryabitsev
2022-10-20 8:49 ` Maxime Ripard
2022-11-09 14:14 ` Maxime Ripard
2022-11-29 17:14 ` Konstantin Ryabitsev
2022-11-29 20:52 ` Maxime Ripard
2023-05-05 7:17 ` Maxime Ripard
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=Y08MuItOLxqpBr+/@sirena.org.uk \
--to=broonie@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=maxime@cerno.tech \
--cc=tools@linux.kernel.org \
--cc=users@linux.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