Migrating from svn to git: tags get a '@' with number at the end of the tag. What can it be?

2

I have a question. I made the project clone with git svn clone . I used git remote add +url to add the remote repository. When I'm doing git push --tags to git the tags are going in a different format than svn. For example:

  • In SVN: tag_all_1.0.0.
  • No GIT (migrated): tag_all_1.0.0@431

Does anyone know what that can be?

    
asked by anonymous 18.06.2018 / 20:50

1 answer

0

I believe the explanation for this occurs with the tags being the same with the branches: Git Svn was not able to find a "parent" commit for the first commit of the SVN branch so that it can connect the branch with the history of the other branches.

This is because SVN allows a branch to be created from any directory that is not necessarily a branch (or trunk) within SVN. For example, copying the directory /trunk/foo to /branches/bar instead of copying from /trunk will give rise to this branch.

The format in which it creates the branch (or tag) is:

<branchname>@<SVN-Revisão>

Now, explaining the source of this review and why Git makes this decision is more complicated . I confess that I read and did not understand very well and, to not simply translate what is said there, I leave the link for read the explanation of the documentation. I think this helps, because it is not so simple to search for information about this problem on Google:).

This happens with tag also because in SVN there is not much difference between branch and tag: both are created by copying directories. Git Svn then reflects the same behavior for both.

How to avoid this situation

In cloning the repository, this branch / tag creation with the at sign ( @ ) can be avoided with the parameter --no-follow-branches .

    
14.12.2018 / 18:11