It looks like the svn branches were pushed to refs/remotes/svn/branchname
not refs/heads/svn/branchname, which is probably why github and clone
doesn't find them.  You're not supposed to push remote-tracking branches,
only local ones.  If you use full push syntax it should work though: `git
push origin refs/remotes/svn/nci:refs/heads/svn/nci`
Also realize that branches can contain slashes... a branch named "svn/nci"
is not the same thing as a remote-tracking branch named
"nci" on a remote named "svn".  The command above pushes the remote-tracking
"nci" on remote "svn" and pushes it to a branch named "svn/nci" on the
remote named "origin".

    Tekkub
    Github Tech Support
    http://support.github.com/
    Join us on IRC: #github on freenode.net
    Discussion group: [email protected]


On Mon, Aug 10, 2009 at 4:23 PM, Chris Wanstrath <[email protected]> wrote:

>
> On Fri, Aug 7, 2009 at 12:38 PM, Jonathan Leto<[email protected]> wrote:
>
> > Lately I have been keeping a git mirror of the Parrot svn repo, and
> > people have asked me to push all the svn branches to github as well.
> > It seems that github will accept branches with a / just fine (as it
> > should), but the web interface borks.
> >
> > (arkham)(~/git/parrot upstream )$ git push github svn/nci
> > Counting objects: 213, done.
> > Delta compression using up to 2 threads.
> > Compressing objects: 100% (76/76), done.
> > Writing objects: 100% (175/175), 29.29 KiB, done.
> > Total 175 (delta 127), reused 139 (delta 91)
> > To [email protected]:leto/parrot.git
> >  * [new branch]      svn/nci -> svn/nci
> >
> > If I then go to my github dashboard, it tells me that a new branch
> > svn/nci has been created, but then the link
> >
> > http://github.com/leto/parrot/tree/svn/nci
> >
> > is a 404.
> >
> > I even tried
> >
> > http://github.com/leto/parrot/tree/svn%2Fnci
> >
> > but that didn't fly either.
>
> Do you have an example I can investigate? I cloned leto/parrot and it
> did not contain a branch called "svn/nci".
>
> You may want to check out our support site for a better response time
> in the future: http://support.github.com/
>
> The mailing list is fine too, though.
>
> Cheers,
> --
> Chris Wanstrath
> http://github.com/defunkt
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"GitHub" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/github?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to