Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org
Subject: b4 trailers doesn't work with imported series
Date: Wed, 7 Dec 2022 00:41:05 +0000	[thread overview]
Message-ID: <Y4/hIf+o/e3AtBCD@sirena.org.uk> (raw)

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

Not a common use case but if I do for example:

| $ b4 prep -F 20221117104636.639889-1-broonie@kernel.org -n tap-spec-relax -f v6.1-rc1
...
| NOTE: any follow-up trailers were ignored; apply them with b4 trailers -u

I run the suggested command but get:

| $ b4 trailers -u
| Calculating patch-ids from commits, this may take a moment...
| Checking change-id "20221207-tap-spec-relax-9138e5760340"
| Grabbing search results from lore.kernel.org
| Nothing matching that query.
| No trailer updates found.

since the change wasn't sent with b4 initially.  I see that the
documentaton does say to use -F but using that produces the same
output, it looks like it's checking the change-id no matter what
and gives up if it can't find it.

BTW I also notice that no template inter-version chnagelog is
generated for the b4 prep command above, the same thing seems to
happen even if the sent series has a cover letter.

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

             reply	other threads:[~2022-12-07  0:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-07  0:41 Mark Brown [this message]
2022-12-07  1:56 ` b4 trailers doesn't work with imported series 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=Y4/hIf+o/e3AtBCD@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=tools@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).