{"thread":{"id":"37470","subject":"Dealing with conflicting tags - multiple remotes","startedAt":"2014-09-01T15:36:22Z","lastAt":"2014-09-01T15:36:22Z","messageCount":1,"participants":["Finucane, Stephen"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"248700","messageId":"6A74A01C3512C646A9ED99AFA28AEB9813F6F138@IRSMSX108.ger.corp.intel.com","threadId":"37470","inReplyTo":null,"subject":"Dealing with conflicting tags - multiple remotes","fromName":"Finucane, Stephen","fromEmail":"stephen.finucane@intel.com","sentAt":"2014-09-01T15:36:22Z","receivedAt":"2014-09-01T15:36:22Z","isPatch":false,"sender":{"key":"stephen.finucane@intel.com","avatar":null},"body":"Hi,\n\nTake a repo with multiple remotes. These remotes each have a specific branch/tag naming convention, and there are tags in each that conflict with those in other remotes. In order to avoid conflicts, it seems possible to add something like this to the '.git/config' file:\n\n    [remote \"origin\"]\n        url = git@github.com:schacon/simplegit-progit.git\n        fetch = +refs/heads/*:refs/remotes/origin/*\n        fetch = +refs/tags/*:refs/tags/origin/*\n\nThis is discussed here:\n\n    http://stackoverflow.com/a/5496610\n    http://git-scm.com/book/en/Git-Internals-The-Refspec\n\nHowever, when you try to pull in these tags, you'll see two different sets of tags - one with the prefix ('origin' above) and one without. Why is this? Is this a bug, or by design?\n\nIf this is not the recommended approach to avoid conflicts, could someone suggest a better one?\n\nRegards,\nStephen Finucane\n\nPS: system info -\n * Fedora 20 64-bit (3.15.7-200.fc20.x86_64)\n * git version 1.9.3\n\n--------------------------------------------------------------\nIntel Shannon Limited\nRegistered in Ireland\nRegistered Office: Collinstown Industrial Park, Leixlip, County Kildare\nRegistered Number: 308263\nBusiness address: Dromore House, East Park, Shannon, Co. Clare\n\nThis e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.\n"}]}