git checkout with an ambiguous rev

Rohit Sarkar· Oct 2, 2019, 12:02 UTC · lore

Hi, I was looking into writing a patch for the issue [1] where if an user has multiple remotes each with a remote tracking branch of the same name say xyz, 'git checkout xyz' fails with "error: pathspec 'xyz' did not match any file(s) known to git."

This can sort of be handled by setting checkout.defaultRemote so that the ambiguity is removed. Although when checkout.defaultRemote is not set or there are more than 2 remotes I think it would be helpful if git gives a message listing out the possible revs instead of the pathspec error. What do you guys think?

[1] : https://public-inbox.org/git/CACcTrKdzVCKUR8EfwhqBQR7vWzRqTLcwRJ_r-hx3VztD=xvNuQ@mail.gmail.com/

Rohit Sarkar· Oct 2, 2019, 13:28 UTC · re: Rohit Sarkar · lore

Re: git checkout with an ambiguous rev

On Wed, Oct 02, 2019 at 05:32:13PM +0530, Rohit Sarkar wrote:

Show 13 quoted lines

> Hi,
> I was looking into writing a patch for the issue [1] where if an user has
> multiple remotes each with a remote tracking branch of the same name say
> xyz, 'git checkout xyz' fails with "error: pathspec 'xyz' did not match any
> file(s) known to git."
> 
> This can sort of be handled by setting checkout.defaultRemote so that
> the ambiguity is removed. Although when checkout.defaultRemote is not
> set or there are more than 2 remotes I think it would be helpful if git
> gives a message listing out the possible revs instead of the pathspec
> error. What do you guys think?
> 
> [1] : https://public-inbox.org/git/CACcTrKdzVCKUR8EfwhqBQR7vWzRqTLcwRJ_r-hx3VztD=xvNuQ@mail.gmail.com/

Nvm. This was already handled in https://github.com/git/git/commit/ad8d5104b42108851b082d895018655ad5f9e4f3 by Avar

Thanks, Rohit