Andy Parkins wrote: > > I'd be arguing for making not following unannotated tags the default, and then > supply a switch to make them followed. Is that too painful? I think that's > in keeping with the tradition that unannotated tags are, typically, not > wanted in a central repository - the default update hook prevents it for > example. > Yup. I share your feelings about simple tags. However, unless the repo owner has decided to explicitly push the simple tag to the repo, or fscked up by doing "git push --all" when he had cruft in his own repo, those tags are in fact part of the repo. In the "oops" case, I'd point this out to the owner so he/she can delete them from the central repo (and enable the update-hook that barfs when simple tags are pushed). If the owner actually wants the tags there, then they're obviously important for some reason, so keeping them might make sense. If anything, I'd be more interested in teaching git how to clean up simple tags. That fix is useful on a wider basis and the "simple vs annotated" recognition code can be useful for skipping unannotated tags when doing "git push --all --not-simple" (or some such). I have no idea where to put it though, as I haven't followed git development very closely as of late. -- Andreas Ericsson andreas.ericsson@xxxxxx OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 - 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