Set default GitHub branch to "2.0"

GitHub provides Subversion bridge, which allows to use SVN client to read (and write) Git repositories. However, currently only the default branch is accessible for SVN. Can you, please, set the default GitHub branch to "2.0" instead of "master" then?

The "master" branch matches the latest release and as such is not equivalent to the former SVN "2.0" development branch. There’s no profit to using a stable branch straight from source version control system. To follow the development, one has to use the real development branch.

I don’t use Git for my projects (and don’t plan to ATM). Anyway, I still want to follow the latest development and run my MODx Revo from Git like I did from SVN.

I don’t use Git for my projects ..

Fair enough, but what reason do you not use Git for? I’m a long time SVN user myself and at the mo I’m still switching projects from SVN to Git. I find Git much better than SVN in nearly all respects, the learning curve is a bit steeper admittedly.

I have a selfish reason for wanting this. I have an extensive section in the book on getting the SVN "bleeding edge" version of MODx. I don’t know if I have time to learn Git and rewrite and test it. I could just put in a note about Git if there were an SVN bridge to the development version.

I agree with Gadamiak that the bridge to the 2.0 version isn’t much use since you can get that version on the download page.

Quote from: shamblett at Aug 18, 2010, 03:02 PM

Fair enough, but what reason do you not use Git for?

Quite simple: Subversion already does all I need. I’m used to it, know it well and have my own infrastructure set already for it, my projects are not public and contain lots (I mean LOTS) of binary files, I don’t share the source with others, and don’t have time to learn Git. Plus, there are no Git clients for Windows good enough to compete with TortoiseSVN.

I just don’t have a need to switch

Besides that, it’s hard to compare a centralized and distributed SVC systems. They are targeted at different strategies and approaches. I do prefer Subversion way, at least for now.

You can learn GIT on a rainy afternoon.

GO to Peepcode and buy for $9 bucks the
Scott Chacon book, GIT Internals that covers
GIT pretty good with all the day by day commands
you need.

Chacon also wrote a new GIT book by APress,
thats is as large as the OReilly GIt book.