From: Rohit Sarkar <rohitsarkar5398@gmail.com>
To: git@vger.kernel.org
Subject: Re: git checkout with an ambiguous rev
Date: Wed, 2 Oct 2019 18:58:32 +0530 [thread overview]
Message-ID: <20191002132832.GD5812@SARKAR> (raw)
In-Reply-To: <20191002120213.GB5812@SARKAR>
On Wed, Oct 02, 2019 at 05:32:13PM +0530, Rohit Sarkar wrote:
> 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
prev parent reply other threads:[~2019-10-02 13:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 12:02 git checkout with an ambiguous rev Rohit Sarkar
2019-10-02 13:28 ` Rohit Sarkar [this message]
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=20191002132832.GD5812@SARKAR \
--to=rohitsarkar5398@gmail.com \
--cc=git@vger.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).