Hi, On Sun, 15 Feb 2009, Junio C Hamano wrote: > Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: > > >> Why? Most tags will be created once and will stay there. That is how > >> tags are supposed to behave, isn't it? > > > > Exactly my point. In the common case, it does not change a thing. > > Wrong. > > In the common case, you will create tons of useless files that waste a > disk block to store 180-byte or so perr each tag. Hmm. My reasoning was that the reflogs will be purged by git gc anyway, and that it might be interesting to be able to know how a tag entered the current repository (if it was not too long ago), but you're probably right on that. > > However in the case that we _do_ change tags, would you not agree that > > the reflog is _the_ place to record the change? > > That merely means whoever changes the tag and wants the record of such an > update, which is uncommon, need to make sure reflog is created for that > tag (and that tag only). The thing is: we cannot. At least not at the moment. I agree that "git tag" should not add a reflog. But one should be able to force "git update-ref" to create a reflog entry, no? Ciao, Dscho -- 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
