{"thread":{"id":"27113","subject":"Strange behaviour of --tags when adding remotes","startedAt":"2011-04-16T10:50:17Z","lastAt":"2011-04-16T10:50:17Z","messageCount":1,"participants":["Timo Schmiade"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"165959","messageId":"20110416105017.GA2887@Discworld","threadId":"27113","inReplyTo":null,"subject":"Strange behaviour of --tags when adding remotes","fromName":"Timo Schmiade","fromEmail":"timo.schmiade@gmx.de","sentAt":"2011-04-16T10:50:17Z","receivedAt":"2011-04-16T10:50:17Z","isPatch":false,"sender":{"key":"timo.schmiade@gmx.de","avatar":null},"body":"Hi all,\n\nI just stumbled upon what I think is a bit of a strange behaviour when\nusing \"git remote add\" with the --tags option. The remote I added was\nfetch'able after the command (it was added to .git/config), but there\nwas no remote tracking branch set up for it (i.e. the\n.git/refs/remotes/<shortname> directory didn't exist).\n\nOnly after removing the \"tagopt = --tags\" option from .git/config was it\nthat \"git fetch <shortname>\" created a remote tracking branch for the\nremote.\n\nAfter double-checking the \"man git-fetch\", I still think this behaviour\nis quite confusing, so I wanted to inform you about this.\n\nKind regards,\n\nTimo\n"}]}