On Fri, Dec 13, 2013 at 22:30:13 +0100, Patrick Ohly wrote:
Correct. I am occasionally setting tags anew when a release
turns out to require further changes. The alternative would be to assign
new versions to each release candidate, but that could lead to an
inflation of version numbers. I'd prefer to stick with the current
approach, even though it can be confusing occasionally.
Perhaps annotated tags avoid this problem - I need to check that.
as often, it's just a matter of proper adjustment of the git
In this case, "git config --local --add remote.<remote name>.fetch
+refs/tags/*:refs/tags/*" did the trick.