On Jun 14, 2009, at 3:45 AM, **Private** wrote: > > ** Private ** wrote: >> I know I've said this before, but if you haven't checked out using >> git >> instead of subversion, you owe it to yourself to try it out. I store >> my origin repo's on my drop box account, other people store their >> repos on a usb key. Try that with subversion! > > Actually, that is just as easy with SVN as with Git. The real > question is why you would want to have your repository somewhere > where the rest of the team can not access it. > Because I can have my own disconnected repo where I can try all kinds of crazy stuff and make all kinds of branches but still not cloud the team repo with all of it. Or., if I'm on the road, I can still have my version control with me and a full history of my project without an internet connection. Have you used git? Last I checked, you had to be running some kind of server to host a subversion repository. It's not so with git.
git init git add . git commit -m "initial commit" and that's all it takes to create my local repository. > >> I've even seen a cms where the history is maintained >> in a git repo. Plus, if you're paranoid like me about losing work, >> the ability to have multiple repos located in different areas and >> easily maintained is awesome. >> >> My current workflow keeps a dev repo on my laptop or desktop. When >> I've finished work for the day, I back my work up to the local repo, >> regardless of whether it works or not and no internet connection is >> required. When all my code is passing the tests, then I push to an >> origin repo located on my dropbox account. > > Sounds like a lot of work. I have multiple SVN repositories in three > different geographic locations that synchronize automagically. I > just commit to the public one and that is automagically synchronized > to the rest. No need for manual backups and copying to different > locations. > > if you consider "git push origin" or "git push secondary", etc to be a lot of work, then maybe so. I don't. This all could be automated too, if needed. >> git is version control that takes the pain out of version control. > > I think the real benefits in using Git are in the quality of its > revision tracking across branches and merges. It is much easier to > figure out where line X in file Y originated then in SVN. Not really > an issue for my current workflows though since we have a branching > and merging policy that is pretty strict. > I base my vimrc and vim dir on a project up on github. I clone the repo to my dev machine, but since I don't care for some of their settings, I change them. I commit my changes back to my own repo, but never push back to the origin. If the github repo is updated, I can still pull down whatever updates are made to it without losing my updates. That is one of my favorite features. I remember trying to use svn the same way...I think with an addin called svk. It never worked that great. > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-community/message.cfm/messageid:298412 Subscription: http://www.houseoffusion.com/groups/cf-community/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.5
