And let's not forget that GIT can't revert changes.
-----Original Message----- From: denstar [mailto:valliants...@gmail.com] Sent: Saturday, 8 May 2010 3:42 AM To: cf-talk Subject: Re: How are other developers handling big SVN repositories? On Fri, May 7, 2010 at 1:41 AM, Andrew Scott wrote: > > Wow you have lost me. Sorry, I'd been drinking. j/k, I'm always this way :) > First let's look at a great Client UI first, SmartGit looks awesome have > been using the SamrtSVN version for awhile but I prefer it inside my IDE > first and foremost. Me too. SmartGit looks pretty nice. Note the comment about not being a 1:1 deal to Git though. :) Since msysgit is the defacto windows git deal now, things are better, but this happened pretty recently. > A lot of things you mention below I am not sure if you are referring to SVN > or GIT, you can certainly hide code in SVN now by just ignoring it. Might > have to look a bit closer how GIT does this. The shelving or "stashing" of code is what I was talking about. It's like a temporary svn ignore, sorta. It's another way of having local changes that you don't commit, basically. > Are you saying that GIT can't check out a part of a project, by revision? I > know you can in SVN so you must be talking about GIT here. Yup, I was referring to Git. You must check out the entire project. All the git metadata is in a single .git folder at the repository root. You can check out to a specific revision, but you gotta do the whole project. Submodules is the Git way of doing svn:externals, but it doesn't seem as powerful. More "all or nothing". > From what I read about GIT and Subversion 1.6 they are almost identical when > it comes to merging and patching code, not having used GIT at this point I > may have to look a bit harder at the differences. > > But SVN is as powerful or not depending on if you utilise that power, and by > the sounds of it GIT is no different in that area as well. Basically. :) > If I have misread what you are trying to say, you didn't make it easy which > parts you are talking about for which application although I see a could > majority of it can be used in SVN. The main difference for me has been that Git can "edit" commits, and doesn't need a network connection. The editing/deleting of commits is powerful but can mess your "team" up if you don't handle it right. A silly impression: SVN is sorta like 1, 2, 3, 4, and Git is like 1, 3, 2, 5 :) :Den -- We have to live today by what truth we can get today and be ready tomorrow to call it falsehood. William James ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael-Dinowitz/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:333510 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
