http://learn.github.com/p/branching.html

because you can do

git branch NET35
git checkout NET35
… do some git stuff and commit …
git push origin NET35

to me that seems more straight forward then the method you took.

in general, the `:’ separates the “source” from the “destination”, so `git pull origin foo:bar’ will pull the “foo” branch down from your remote, while naming it locally “bar”; whereas `git push origin bar:foo’ will push your local “bar” branch to your remote as “foo”.

You can also delete a remote branch by doing `git push origin :foo’, which will delete the foo branch (it essentially says “push nothing up to my remote origin as ‘foo’” – Yoda speak for “delete foo”).

You may already know most of that, but I figured I’d share. GitHub has a good reference here:
http://help.github.com/remotes/

-Charles

Yep, you have to internalize at least a lot of things. Pull down the source and you can see how I got it to work. But I also deploy the non-merged versions, in case folks need a later version of Castle or something

@Alastair

I didn’t think that a local branch could be pushed to a remote server branch that doesn’t exist yet. Is that possible?