Re: [PATCH] push: disallow fast-forwarding tags without --force

Dave Olszewski [off-list ref] writes:

Generally, tags are considered a write-once ref (or object), and updates
to them are the exception to the rule.  This is evident from the
behavior of "git fetch", which will not update a tag it already has
unless --tags is specified, and from the --force option to "git tag".

The title and what you describe later in your proposed log message do not
match.  This is about "push: disallow updating an existing tag by default"
isn't it?

This proposes a big change in the policy, and I do not like it starting
out as the new default to forbid people from doing something they have
been allowed to do for a long time.  I recall hearing some people auto
tagging the latest version their autobuilder/tester tested successfully
and updating the same tag nightly---your change will break their cron
script, no?

If you ship the feature disabled by default first, it will still allow
people to take advantage of it by simply flipping the feature on, instead
of having to install their own update hook.  In a later version, if and
when enough people agree that this should be on by default, we can do so
at a version bump.