Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime@cerno.tech>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: users@linux.kernel.org, tools@linux.kernel.org
Subject: b4 bugs / future improvements
Date: Tue, 18 Oct 2022 17:36:20 +0200	[thread overview]
Message-ID: <20221018153620.tyuedbldi2ofbe2x@houat> (raw)

[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]

Hi Konstantin,

Thanks again for b4, it's really great :)

There's a bunch of things I have noticed in the recent weeks:

 - It looks like 87e0e464959c breaks msmtp which doesn't recognize the
   -f option, and will just error out

 - 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?

   - If one sends a version, rebases, and then runs b4 trailers -u, then
     no tag is found for that series. I assume it's because the
     change-id has changed, but maybe for series that differ from the
     last sent version we could also look for the last sent change-id?

And finally, and this is more of a feature request, now that it looks
like we have the list of all the older versions in the cover letter and
their base, could we have a subcommand to start a range-diff between an
older version and its base, and the current base and HEAD?

Thanks!
Maxime

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

             reply	other threads:[~2022-10-18 15:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18 15:36 Maxime Ripard [this message]
2022-10-18 20:18 ` b4 bugs / future improvements Konstantin Ryabitsev
2022-10-18 20:29   ` Mark Brown
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=20221018153620.tyuedbldi2ofbe2x@houat \
    --to=maxime@cerno.tech \
    --cc=konstantin@linuxfoundation.org \
    --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