Robert Dailey <rcdailey.lists@xxxxxxxxx> writes: >> > more clear in the doc and/or in the proposed log message what >> > practical downside there are to the end users if we do not stop this >> > "mistake", that is. >> >> Having said all that, I can sort-of see that it may make sense to >> forbid tagging anything but a commit-ish, either by default, or a >> "git tag --forbid-no-committish" that can be turned on with a >> configuration. > > I don't really understand what part of the change is a negative for > you. Are you saying that `git tag` should peel the tags for you? Or > are you saying you don't like nested tagging to be opt-in and an error > otherwise? No, no and no. I am saying "git tag -a -m 'message' tag anothertag" that creates a tag that points at another tag is perfectly fine.
