From: "Mark Brown" <broonie@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org
Subject: b4 ty issues matching remote branches
Date: Fri, 15 May 2020 19:05:42 +0100 [thread overview]
Message-ID: <20200515180542.GM5066@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 573 bytes --]
Hi Konstantin,
Having updated to the latest master a command like
b4 ty -b remote/foo -a
has started to report errors like
Requested branch asoc/for-5.7 not found in git branch --list --all
This is true since "git branch --list --all" lists remotes as
remotes/name/branch while most git commands accept name/branch (and git
branch -r lists them as such). For some reason tweaking to add a
remotes/ on the front doesn't seem to work either, even though grepping
the output appears to confirm that the branch is there under that name.
Thanks,
Mark
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 499 bytes --]
next reply other threads:[~2020-05-15 18:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 18:05 Mark Brown [this message]
2020-05-15 18:31 ` b4 ty issues matching remote branches Konstantin Ryabitsev
2020-05-15 19:28 ` 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=20200515180542.GM5066@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 NNTP newsgroup(s).