Tags were not transferred from svn to git repo

Issue #56 closed
Ferry Huberts created an issue

No description provided.

Comments (9)

  1. IJabz repo owner

    Sorry but I had enough trouble converting the project and the issues in the first place. I dont know how to convert the tags and I cant think they were terribly useful anyway I hardly every used them.

  2. Ferry Huberts reporter

    You now have a different tree than before. Conversion would have been easiest with 'git svn clone'. Tags are now more difficult to transfer because of the different trees

  3. Ferry Huberts reporter

    I've transcribed the tags and the 2.0.2 branch, you can fetch them from my clone at https://bitbucket.org/fhuberts/jaudiotagger

    • [new branch] 2.0.2 -> 2.0.2
    • [new tag] Build1004 -> Build1004
    • [new tag] Version1 -> Version1
    • [new tag] jaudiotagger-2.1.0 -> jaudiotagger-2.1.0
    • [new tag] v1.0.1 -> v1.0.1
    • [new tag] v1.0.2 -> v1.0.2
    • [new tag] v1.0.5 -> v1.0.5
    • [new tag] v2.0.2 -> v2.0.2
    • [new tag] v2.0.3 -> v2.0.3
    • [new tag] v2.1.0 -> v2.1.0
  4. IJabz repo owner

    Okay thankyou but I have clicked on them via the bitbucket interface but cannot see anyway to merge the commit into my repos. Can you explain how I do this, would it easier if you make a pull request. (sorry really dont know much about git)

  5. Ferry Huberts reporter
    cd <your jaudiotagger checkout>
    git remote add fhuberts https://bitbucket.org/fhuberts/jaudiotagger.git
    git fetch fhuberts
    git fetch fhuberts --tags
    

    You can then push the new tags and the new branch

  6. Ferry Huberts reporter

    There was a 2.0.2 branch in the old repo. I've transcribed that one as well

    cd <your jaudiotagger checkout>
    git branch 2.0.2 fhuberts/2.0.2
    

    You can then push the branch

  7. IJabz repo owner

    Okay that was a mistake it makes no sense for me to have different branches for different versions just tags so I'll not add that.

  8. Log in to comment