Git Repository Information

[Joe]

What?! The project isn't dead?! No you fool! At least not this week!

I'm using Git for all of my school stuff and I like the system a lot better than SVN. Therefore, if I want to work on JavaOp without SCM getting in the way (at least, as little as possible), I need to use Git. K? K.

Github is a site that offers free hosting of public repositories, or for-pay hosting of private repositories. You can find JavaOp2 here, with instructions to check it out. As usual, if you feel you should have commit rights to the project, contact me.

The SVN repository will remain available as long as Google exists.

[deadly7]

You can also use git to clone an SVN repo..

[Joe]

I found that to be particularly neat. All the commits were saved from Google Code.

[deadly7]

I found that to be particularly neat. All the commits were saved from Google Code.

You're misunderstanding. The syntax is "git svn init <svn-url>"  and then you can use git without making a new repository. It's pretty handy because you can work it with both svn and git.

[Joe]

Ooh! I like.

[deadly7]

Ooh! I like.

Yeah. Git is ridiculously powerful. Just has funny syntax.
svn update === git svn rebase

and to commit you do the usual
"git add"
"git commit" [or git commit -m]
"git dcommit" to submit things on your local branch to the master.

Branching with git/svn is much more a PITA and usually not worthwhile, in my experience

[Sidoh]

If you're working alone, branching is awesome.  If you're starting on something you know could fuck things up, it makes it easy to revert to a stable state.  Of course you can do that without branching, but it certainly makes it a little easier.

I've also had a little experience using branching with subversion on a project with about half a dozen developers.  It works really well, as long as there aren't too many changes to the same file.

[iago]

Is it safe to delete my old javaop svn stuff? I'm cleaning up my svn server right now, will get rid of it if it's safely in git.

[Joe]

Yep