On Mar 2, 11:59 pm, Trans <transf...@gmail.com> wrote:
> Can anyone here tell me of cases when they felt its was necessary to
> re-tag a repo (with the same tag as had been used previously)?
> Git allows this, though in the docs it clearly warns against it,
> especially if you have pushed the tags. But it still does not forbid
> it and even provides a way to delete remote tags if need be. Is that
> such a bad idea that git should remove this feature? Or are their
> legitimate reasons/scenarios to let the developer this flexability?
The legitimate reasons for this flexibility is providing flexibility
-- as simple as that.
Re-tagging is not the only thing you can do -- for instance, with
default install you can easily delete (almost) any branch from the
remote repo or "forcibly update" it (read: replace).
This really provides an extra level of flexibility and I, personally,
had several cases when replacement of tags and branches appeared to be
the best solution.
If you're looking at implementing a centralised repository (say, in a
company) which must not allow such kinds of tricks due to some
enforced policy, look at Git hooks which seem to be able to provide a
great deal of control for what happens with the repository.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To post to this group, send email to git-us...@googlegroups.com.
To unsubscribe from this group, send email to
For more options, visit this group at