From: Mark Brown <broonie@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org
Subject: b4 prep HEAD fails when specifying branch point
Date: Tue, 6 Dec 2022 22:07:19 +0000 [thread overview]
Message-ID: <Y4+9Fz7lkzSnFV72@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1130 bytes --]
Using Debian bullseye with backports of git installed to get
filter-branch if I attempt to run b4 prep it refuses to create a
new branch saying:
| $ b4 -d prep -n b4-test -f v6.0-rc3
| Running git --no-pager status --porcelain=v1 --untracked-files=no
| Running git --no-pager symbolic-ref -q HEAD
| Running git --no-pager config -z --get-regexp branch\.master\..*
| Running git --no-pager rev-parse --show-toplevel
| Running git --no-pager config -z --get-regexp b4\..*
| Running git --no-pager config -z --get-regexp gpg\..*
| Looking for the cover letter commit with magic marker "--- b4-submit-tracking ---"
| Running git --no-pager log --grep --- b4-submit-tracking --- -F --pretty=oneline --max-count=1 --since=1.year
| Running git --no-pager config -z --get-regexp user\..*
| Running git --no-pager symbolic-ref -q HEAD
| Running git --no-pager symbolic-ref -q HEAD
| Running git --no-pager config -z --get-regexp branch\.master\..*
| CRITICAL: fork-point %s is not on the current branch.
| Switch to the branch you want to use as base and try again.
AFAICT this happens no matter what fork point is specified.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-12-06 22:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 22:07 Mark Brown [this message]
2022-12-06 22:15 ` b4 prep HEAD fails when specifying branch point Konstantin Ryabitsev
2022-12-06 22:58 ` Mark Brown
2022-12-07 1:11 ` Konstantin Ryabitsev
2022-12-07 12:42 ` Mark Brown
2022-12-07 22:55 ` Mark Brown
2022-12-06 23:52 ` Feature requests Mark Brown
2022-12-09 21:09 ` Konstantin Ryabitsev
2022-12-12 12:22 ` Mark Brown
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+9Fz7lkzSnFV72@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).