Git - fatal: Branch name doesn't conform to GIT standards












9














I am trying to migrate a CVS repo to Git using cvs2git.
Unfortunately my cvs repo has many branches with regex.
While doing git fast import(unix) it reports the error below



fatal: Branch name doesn't conform to GIT standards: refs/tags/Release21_3_4_0_0_3_7_10[3_8_4_3]
fast-import: dumping crash report to .git/fast_import_crash_27083


I tried to delete these tags, but no luck. i think it is taking the entire history.
I am not able to import the HEAD alone also.



How do i resolve this?










share|improve this question
























  • You could try this out, if you haven't already: stackoverflow.com/a/10020482/26396
    – Enrico Campidoglio
    Jan 28 '15 at 9:49
















9














I am trying to migrate a CVS repo to Git using cvs2git.
Unfortunately my cvs repo has many branches with regex.
While doing git fast import(unix) it reports the error below



fatal: Branch name doesn't conform to GIT standards: refs/tags/Release21_3_4_0_0_3_7_10[3_8_4_3]
fast-import: dumping crash report to .git/fast_import_crash_27083


I tried to delete these tags, but no luck. i think it is taking the entire history.
I am not able to import the HEAD alone also.



How do i resolve this?










share|improve this question
























  • You could try this out, if you haven't already: stackoverflow.com/a/10020482/26396
    – Enrico Campidoglio
    Jan 28 '15 at 9:49














9












9








9







I am trying to migrate a CVS repo to Git using cvs2git.
Unfortunately my cvs repo has many branches with regex.
While doing git fast import(unix) it reports the error below



fatal: Branch name doesn't conform to GIT standards: refs/tags/Release21_3_4_0_0_3_7_10[3_8_4_3]
fast-import: dumping crash report to .git/fast_import_crash_27083


I tried to delete these tags, but no luck. i think it is taking the entire history.
I am not able to import the HEAD alone also.



How do i resolve this?










share|improve this question















I am trying to migrate a CVS repo to Git using cvs2git.
Unfortunately my cvs repo has many branches with regex.
While doing git fast import(unix) it reports the error below



fatal: Branch name doesn't conform to GIT standards: refs/tags/Release21_3_4_0_0_3_7_10[3_8_4_3]
fast-import: dumping crash report to .git/fast_import_crash_27083


I tried to delete these tags, but no luck. i think it is taking the entire history.
I am not able to import the HEAD alone also.



How do i resolve this?







git cvs2git






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 9 '15 at 4:08









mu 無

40k2594136




40k2594136










asked Jan 21 '15 at 10:10









user2164525user2164525

3471313




3471313












  • You could try this out, if you haven't already: stackoverflow.com/a/10020482/26396
    – Enrico Campidoglio
    Jan 28 '15 at 9:49


















  • You could try this out, if you haven't already: stackoverflow.com/a/10020482/26396
    – Enrico Campidoglio
    Jan 28 '15 at 9:49
















You could try this out, if you haven't already: stackoverflow.com/a/10020482/26396
– Enrico Campidoglio
Jan 28 '15 at 9:49




You could try this out, if you haven't already: stackoverflow.com/a/10020482/26396
– Enrico Campidoglio
Jan 28 '15 at 9:49












1 Answer
1






active

oldest

votes


















3














You can find out more here. This is how git verify that your branch name is a valid name.



The problem is the characters.
Try to locally create branch with those names and you will see the error.



Here is a detailed post(s) abot what and how to do it.



Git try to create branch with the given name



You must rename the tags in order to get them into git.






share|improve this answer





















    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f28064477%2fgit-fatal-branch-name-doesnt-conform-to-git-standards%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    3














    You can find out more here. This is how git verify that your branch name is a valid name.



    The problem is the characters.
    Try to locally create branch with those names and you will see the error.



    Here is a detailed post(s) abot what and how to do it.



    Git try to create branch with the given name



    You must rename the tags in order to get them into git.






    share|improve this answer


























      3














      You can find out more here. This is how git verify that your branch name is a valid name.



      The problem is the characters.
      Try to locally create branch with those names and you will see the error.



      Here is a detailed post(s) abot what and how to do it.



      Git try to create branch with the given name



      You must rename the tags in order to get them into git.






      share|improve this answer
























        3












        3








        3






        You can find out more here. This is how git verify that your branch name is a valid name.



        The problem is the characters.
        Try to locally create branch with those names and you will see the error.



        Here is a detailed post(s) abot what and how to do it.



        Git try to create branch with the given name



        You must rename the tags in order to get them into git.






        share|improve this answer












        You can find out more here. This is how git verify that your branch name is a valid name.



        The problem is the characters.
        Try to locally create branch with those names and you will see the error.



        Here is a detailed post(s) abot what and how to do it.



        Git try to create branch with the given name



        You must rename the tags in order to get them into git.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Feb 12 '15 at 18:34









        CodeWizardCodeWizard

        50.9k126889




        50.9k126889






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f28064477%2fgit-fatal-branch-name-doesnt-conform-to-git-standards%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Bressuire

            Vorschmack

            Quarantine