Linux maintainer tooling and workflows
 help / color / Atom feed
* b4 ty issues matching remote branches
@ 2020-05-15 18:05 Mark Brown
  2020-05-15 18:31 ` Konstantin Ryabitsev
  0 siblings, 1 reply; 3+ messages in thread
From: Mark Brown @ 2020-05-15 18:05 UTC (permalink / raw)
  To: Konstantin Ryabitsev; +Cc: tools


[-- 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 --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: b4 ty issues matching remote branches
  2020-05-15 18:05 b4 ty issues matching remote branches Mark Brown
@ 2020-05-15 18:31 ` Konstantin Ryabitsev
  2020-05-15 19:28   ` Mark Brown
  0 siblings, 1 reply; 3+ messages in thread
From: Konstantin Ryabitsev @ 2020-05-15 18:31 UTC (permalink / raw)
  To: Mark Brown; +Cc: tools


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

On Fri, May 15, 2020 at 07:05:42PM +0100, Mark Brown wrote:
> 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.

I think I was trying too hard. I've committed a small fix to current 
master -- that should relax our sanity-checking logic.

-K

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: b4 ty issues matching remote branches
  2020-05-15 18:31 ` Konstantin Ryabitsev
@ 2020-05-15 19:28   ` Mark Brown
  0 siblings, 0 replies; 3+ messages in thread
From: Mark Brown @ 2020-05-15 19:28 UTC (permalink / raw)
  To: Konstantin Ryabitsev; +Cc: tools


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

On Fri, May 15, 2020 at 02:31:23PM -0400, Konstantin Ryabitsev wrote:

> I think I was trying too hard. I've committed a small fix to current 
> master -- that should relax our sanity-checking logic.

That works, thanks!

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, back to index

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-05-15 18:05 b4 ty issues matching remote branches Mark Brown
2020-05-15 18:31 ` Konstantin Ryabitsev
2020-05-15 19:28   ` Mark Brown

Linux maintainer tooling and workflows

Archives are clonable:
	git clone --mirror https://lore.kernel.org/tools/0 tools/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 tools tools/ https://lore.kernel.org/tools \
		tools@linux.kernel.org
	public-inbox-index tools

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.linux.tools


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git