2011/2/14 Junio C Hamano <gitster@xxxxxxxxx>: > The description in config.txt for --tags also cites another purpose, > namely, to fetch tags otherwise totally unrelated to the branches you are > following, but in reality there is no sensible use case to require such a > feature. Yes, you may have many unrelated lines of development with > separate set of tags on them, but then --tags to fetch _all_ tags from > all of these unrelated lines of development is a too coarse-grained tool > to be useful. > FWIW, here's my use case: I'm doing development on two separate computers, and I'm synchronizing my work between those by fetching from each other computer directly (not pushing through a common repo), i.e. "git remote add other b:/home/me/foo/.git" in ~/foo/.git on computer a and "git remote add other a:/home/me/foo/.git" on computer b. Now I often drop partial work, rebase it etc., and make tags before the dropping, and sometimes I want to revisit those tagged (but not otherwise reachable) commits, and for that I want them to be available on both computers. I too searched the config docs, tried "tagopts = --tags" and then wondered why it wouldn't sync my branches anymore, then moved to "fetch = +refs/tags/*:refs/tags/*". Christian. -- 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