Subversion

[thelusiv]

It would be advantageous for anyone wanting to use the soon-to-be-setup VDrift repository to familiarize yourself with the Subversion Book especially the chapters on using svn. It's not quite like CVS. I'm still poring through it myself, hoping that I can learn enough to get a usable repository set up tonight.

[Tom]

What about using git?

Code:

git svn clone --stdlayout http://svn.vdrift.net/repos/vdrift vdrift.svn2git

after waiting a long time ;-) you update your repository with

Code:

git svn rebase

[joevenzon]

Why git? SVN seems to be working OK.

[Tom]

The biggest advantage is branching.
If you hack on something, you can easily create a branch to do so and not anything on top of trunk or copy the folder somewhere…
Furthermore you see with e.g.

git diff master

what excectly changed.

Another thing, I like, is that you can commit everywhere without internet connection to you local repository. After you get online again, you can push it to the public repository.

I 'personally' like git far more and will use

git svn *

Give it a try ;-)

http://whygitisbetterthanx.com/

[fudje]

I do love the diagrams in the "Any Workflow" section (How to Make Your Project Look Like Fascism).

Now don't get me wrong, I'm all for git (once you've got used to it, it is pretty cool), but as this project goes, it's a solution looking for a problem; One that would require a radical change in how the project authors use revision control systems. Seeing as how there's neither a whole lot of work being done in parallel by a lot of coders nor a gargantuan code base* - such as in the Linux kernel for which git was created - there's not a huge need for a system that does fast offline local branching the way git does.

*Well there's the data repository, that's pretty big. But then, you don't tend to have multiple people working on the same file in it at once.

[Tom]

Fast offline branching is just one advantage I mentioned. It's up to anyone to choose, what works better for anyone. With git svn ist just possible to keep the infrastructure with svn server and so on and to test git.

it's a solution looking for a problem

Not really… The project authors need/can decide to switch to git (where is no need to do so) and anyone can try git svn. I don't see a problem at all.

I'm pretty new to vdrift, but what I saw in some topics was, that peoble submit here the code to get it implemented in svn.

Wouldn't it easier to use patches? (Maybe I just missed something) :roll: