Thread (1 message) 1 message, 1 author, 2016-06-15

Re: Surprising 'git-describe --all --match' behavior.

From: Sergei Organov <hidden>
Date: 2016-06-15 23:01:42

Junio C Hamano [off-list ref] writes:
Sergei Organov [off-list ref] writes:
quoted
Will something break if it won't helpfully prepend refs/tags/ once
--all is given?
"describe --all --match 'v*'" will no longer match a tag v1.2.3, and
forces the users to say "describe --match 'refs/tags/v*'",
No,

descirbe --match 'v*'

or

describe --tags --match 'v*'

depending on what they actually meant. Notice my "once --all is given"
above. 

Those who used --all meant to match against all the refs, no?
and these users will probably see it as a new breakage, I would imagine.
But why would anybody use --all --match if they only meant --tags
--match or even just --match alone? Was it historically --all that was
first introduced, maybe? 

-- 
Sergei.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help