On Sat, Oct 1, 2011 at 20:22, Peter Shenkin <shenkin@xxxxxxxxx> wrote: > > The question is not how the --tags option should be > documented, but rather why "--tags" should behave > differently when the refspec is given on the commandline > than when the refspec is given in the .git/config file. Again, see here: [PATCH v3] Docs: Clarify the --tags option of `git fetch' Message-ID: <686c38876d5a4ad6bfac67ca77fe9bb3-mfwitten@xxxxxxxxx> http://article.gmane.org/gmane.comp.version-control.git/181887 namely: This option is merely a shorthand for writing the refspec `refs/tags/\*:refs/tags/\*'; that is, git fetch origin --tags git fetch origin --tags frotz are equivalent to: git fetch origin 'refs/tags/*:refs/tags/*' git fetch origin frotz 'refs/tags/*:refs/tags/*' In other words, by writing "--tags", you are actually writing "refs/tags/\*:refs/tags/\*"; because you are stating an *explicit* refspec, "git fetch" doesn't bother with any *implicit* default in your config, which is consistent with how "git fetch" works. It would probably be a good idea if there were a "--defaults", too. -- 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