Matthieu Moy <Matthieu.Moy@xxxxxxxxxxxxxxx> writes: > Junio C Hamano <gitster@xxxxxxxxx> writes: > >> I recall "fetch --tags" was updated to become your "--tags-also" by >> e66ef7ae (Merge branch 'mh/fetch-tags-in-addition-to-normal-refs', >> 2013-12-12). Perhaps we should do the same on the push side. > > Would we still have a way to push tags only with this? > > fetch and push are a bit different: it's almost never a bad idea to run > fetch (I see remote-tracking as a kind of cache, and fetch is the way to > refresh this cache), but pushing too much can be harmful. Not a strong > objection, but I'm not sure that this change is 100% safe for everyone. Whether the user is familiar with "git fetch --tags" or not, "git push --tags" that is not spelled as "git push 'tags/*'" does look like an option that augments what the command normally does, and the "mistaken" (non-)bug report was very understandable. After having thought about this, I would say that it would not add much value to the system if we add it as "git push --tags-also". We should either keep the current semantics as-is, or we replace "git push --tags" to make it similar to what "git fetch --tags" does, I think. -- 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