[Bf-committers] Are our git tags out of date?

Sergey Sharybin sergey.vfx at gmail.com
Sun Nov 24 15:11:20 CET 2013

git describe master gives latest tag which is reachable from the HEAD
of master branch. And the thing is: in svn we've created a tag from
trunk and backported several commits there before actual release.

What happened during svn->git converts is that every release have own
branch created at the same moment as tag happend in svn. Then all the
revision were backported to git branch. Tag was created in git branch
and it totally corresponds state of svn state.

Such tags for sure are not reachable from the master branch and that's
why you can not see them with git describe. Not a bug, just different
in how tags are handled in svn and git. Nothing to worry about i'd

On Sat, Nov 23, 2013 at 6:52 PM, Dan McGrath <danmcgrath.ca at gmail.com> wrote:
> While watching an advanced git video (which btw, is a nice follow up to the
> Git video by Scott from the other day):
>   https://www.youtube.com/watch?v=ig5E8CcdM9g
> I noticed that when he got to the section on tags vs. annotated tags (~30+
> minutes in, iirc), that the command:
>   git describe master
> gave the output:
>   v2.66-6202-g2cb6348
> This got me to thinking that maybe we are missing a few annotated tags (git
> tag -a <rev>) in the repo?
> Anyways, just something I noticed and thought that I would inquire about,
> and also to point out an amazing advanced git video! o/
> Dan
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers

With best regards, Sergey Sharybin

More information about the Bf-committers mailing list