I'm preparing to give a git course and came across the following situation. Suppose I add two *completely* *independent* remotes to my local repository (no shared history) with the goal to make a subtree merge:
git remote add example https://example.com/repo.git git remote add example2 https://example2.com/other.git Coincidentally they both have a tag named "v1.0.0" which point to different commits (both histories are unrelated). Now I fetch both remotes: git fetch example git fetch example2 When I list all tags, I only get one v1.0.0 tag. Only the tag of the first repo is visible! When I did the second fetch, git thought the tag was already there. - How would I refer to the v1.0.0 tag of example2 (without using the SHA1 hash of course)? - Is this a limitation or is this by design? - Why are remote branches prefixed with a name (e.g. example/master and example2/master) but the tags not? Please enlighten me! -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
