On 2011.02.13 10:17:48 +0100, Ævar Arnfjörð Bjarmason wrote: > Also because you specified --tags you're only getting the tags on "git > fetch" That looks like a bug to me. It's ok for fetch to treat --tags like a refspec and to have it override the defaults from the config when the user manually specifies it on the command line. But when it is part of the default configuration it should add to remote.<name>.fetch, not override it. IOW with this configuration: remote.foo.url = git://host/repo.git remote.foo.fetch = +refs/heads/*:refs/remotes/foo/* remote.foo.tagopt = --tags "git fetch foo" acts like: git fetch --tags git://host/repo.git instead of git fetch --tags git://host/repo.git +refs/heads/*:refs/remotes/foo/* And I'd argue that the latter makes a lot more sense. Also because the former could always be achieved by dropping the remote.foo.fetch config setting. Thoughts? Björn -- 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