"Aneesh Kumar K.V" <aneesh.kumar@xxxxxxxxxxxxxxxxxx> writes: > With an entry like below > > [remote "github"] > fetch = +refs/tags/*:refs/tags/origin/* > url = git://github.com/kvaneesh/QEMU.git > > when i do git fetch github for-anthony i get the below error When you give refspecs from the command line like that, the default refspec remote.github.fetch will not be used and what you configure there is immaterial. > [master@QEMU]$ git fetch github for-anthony >>From git://github.com/kvaneesh/QEMU > * tag for-anthony -> FETCH_HEAD Sounds sane. Does "git cat-file -t FETCH_HEAD" report "tag" (it should)? After doing that fetch and inspecting "git log -p ..FETCH_HEAD", you should be able to do "git merge FETCH_HEAD" and it should be like you did "git pull github for-anthony". > Also trying to do > > [master@QEMU]$ git fetch git://github.com/kvaneesh/QEMU.git for-anthony:aneesh/for-anthony > error: Trying to write non-commit object 12916047784615b7d8b879d9d39be6c1559e1b1b to branch refs/heads/aneesh/for-anthony >>From git://github.com/kvaneesh/QEMU > ! [new branch] for-anthony -> aneesh/for-anthony (unable to update local ref) > * [new tag] for-anthony -> for-anthony Sounds sane, too. > I understand that replacing the above with below works. But we should > not be required to specify refs/tags there right ? > > [master@QEMU]$ git fetch git://github.com/kvaneesh/QEMU.git refs/tags/for-anthony:refs/tags/aneesh/for-anthony If the "for-anthony" name is ambiguous between branches and tags, then you must disambiguate. I am guessing that the unqualified LHS "for-anthony" is found in the branch namespace of the remote, and that is why RHS is qualified with the same refs/heads/ prefix to store it to the branch namespace. On the other hand, if "for-anthony" name is unambiguous, then you may have found a bug. I cannot tell. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html