From: "Mark Brown" <broonie@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org
Subject: b4 ty doesn't respect -b for prs
Date: Wed, 22 Apr 2020 15:06:37 +0100 [thread overview]
Message-ID: <20200422140637.GI4898@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 656 bytes --]
Hi Konstantin,
When I run b4 ty to generate thank-you letters for a pull specifying -b
the program doesn't find the merge commit:
$ b4 ty -b asoc-5.7 -s 2
Generating 1 thank-you letters
Could not get merge commit id for [GIT PULL] ASoC: tegra: Fixes for v5.7-rc3
Was it actually merged?
however if I change to the branch it does:
$ git checkout asoc-5.7
Switched to branch 'asoc-5.7'
$ b4 ty -b asoc-5.7 -s 2
Generating 1 thank-you letters
Writing: ./thierry_reding_gmail_com_git_pull_asoc_tegra_fixes_for_v5_7_rc3.thanks
(asoc-5.7 is for-5.7 in my sound tree, the merge commit is now published.)
Thanks,
Mark
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 499 bytes --]
next reply other threads:[~2020-04-22 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 14:06 Mark Brown [this message]
2020-04-22 22:43 ` b4 ty doesn't respect -b for prs Konstantin Ryabitsev
2020-04-23 10:17 ` Mark Brown
2020-04-23 15:07 ` 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=20200422140637.GI4898@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