{"thread":{"id":"36049","subject":"Confgure option like tagopt=note to notice changed remote tags","startedAt":"2014-03-04T15:42:54Z","lastAt":"2014-03-04T15:42:54Z","messageCount":1,"participants":["Alexander Holler"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"235998","messageId":"5315F47E.3040801@ahsoftware.de","threadId":"36049","inReplyTo":null,"subject":"Confgure option like tagopt=note to notice changed remote tags","fromName":"Alexander Holler","fromEmail":"holler@ahsoftware.de","sentAt":"2014-03-04T15:42:54Z","receivedAt":"2014-03-04T15:42:54Z","isPatch":false,"sender":{"key":"holler@ahsoftware.de","avatar":null},"body":"Hello,\n\nalso I'm using git since a long time, I can't remember that I've noticed \nthat git doesn't make a note or warning if remotes tags have changed.\n\nE.g. what's often will be forgotten is to annotate tags before pushing \nthem. The usual resolution is just to annotate them locally and push \nthem again.\n\nBut such a change never ends up at people which already have fetched the \ntag (without them using git fetch -t). They even don't receive a notice \nwhich could remind them to use git fetch -t.\n\nUnfortunately I'm not aware a lot about git internals, but would it be \nhard to make it configurable (tagopts comes into mind) that git outputs \na warning if a remote tag and local tag do disagree about the commit, \nannotation or sign? I even would prefer such a warning as the default.\n\nRegards,\n\nAlexander Holler\n"}]}