Development > Newbie Coding
Switch from svn to git without redownloading everything?
Destructavator:
--- Quote from: Muton on October 05, 2010, 08:14:47 pm ---I want to break a lance for Mattn
The move to git was the right thing to do
Merging code is a torture under svn
merging a fork is :P
The older MsysGIT was bugged the new 1.7.? does its job
and adding Git was not a software problem.
Its a Layer8 problem, but thats normal for a Svn->Git move
I stuck because i dont know what mattn is doing/planing
C::B support seems to be dropped and native MinGW compiling isnt possible
--- End quote ---
Well, even if the old system made merging a pain, the new one seems worse - not only can I still not commit any changes yet (I'm still fighting with this awful software), but I can't even get a read-only copy to update once in a while. Even if I don't make any commits or changes at all, it will only update once or twice before bombing with errors and becoming useless, forcing me to delete the whole directory and re-download the whole thing again. I've tried everything from fetch, to rebase, to pull, to using other third-party "helper" utils and I still can't make it work. Oh, and BTW, yes, I have been reading guides and documentation, so I'm not some ignorant character who can't make it work simply because they don't read instructions.
There are other alternatives that SF servers support, for example Mercurial, although I admit I haven't researched all of them - but there's much more than just SVN, CVS, and Git.
I'm really hoping Mattn will read this thread and soon tell us what the game plan will be. Yes, I've also noticed the Windows compiling/build and other support really go down the toilet recently. The move to Git is just another example of this trend.
H-Hour:
I use Windows and have no problem using the Gitbash interface that comes with whatever it is we were told to download (msysgit I think, but the program is called GitBash on my system - shows you how little I know about this stuff). You're right, TortoiseGIT is not really mature yet, but you don't need it either. It does the few things that it's really helpful for Windows users to have (selecting several different files in a folder rather than performing adding via command line, for instance). The rest is just as simple (actually, I would say more simple) via the command line interface: fetching and pushing. I use TortoiseGIT as little as possible (basically, I add new files and create a commit only with it).
For artists -- whether sound, model or mapping -- distributed control systems like this are often much more complicated than needed, for the simple reason that it's unlikely that one person will be working on the reverb while another completes the guitar riffs, or I will be painting the head on a body model while someone else paints the shoes. We don't need simultaneous access to single files and a system that can manage simultaenous changes. But that's exactly what the coders need, and for that merging and all the other stuff is incredibly important.
--- Quote from: Destructavator on October 05, 2010, 08:34:34 pm ---Yes, I've also noticed the Windows compiling/build and other support really go down the toilet recently.
--- End quote ---
Of course when a major change like this happens that renders several tools non-functioning, it will take a while to bring them back up to speed. The same thing has happened in non-Windows areas, like the web-based info on licensing used for GPL'ing textures, the map-get.py script, etc. Yet many of them are already back online, and entirely new build systems are being put in place now.
Thrashard96:
+1 SVN
Mattn:
i don't think the git move was wrong. and i don't think git is bugged or anything like that, i'm using the official git installer and it works fine on win32.
also the git move was researched before. i've looked at some other dvcs before we decided to use git. for those of you who are "only" fetching the latest dev version from the repo: you don't even have to compile (use the nightly build binaries), nor checkin - so where is the problem? and yes, maybe some of you find svn easier than git - but a vcs is there to support the devs - and git is more advanced than svn to help every dev who knows how to handle it. i've never said it wouldn't need some learning - but i've always said that it's worth it.
also i don't see why this step should screw new contributors? getting the source, creating a patch, submit a patch. it's in no way different from the svn workflow, isn't it? (it's just git format-patch and not svn diff)
Mattn:
@Muton: C::B is not yet dropped, but i would like to drop it. what is the exact problem with mingw compilation? (or is it "only" about the static libs?)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version