http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660I'll just get me coat then... http://ayende.com/3289/thoughts-about-building-your-own-source-control#comment11http://ayende.com/3289/thoughts-about-building-your-own-source-control#comment11Fri, 02 May 2008 08:34:05 GMTDon't forget to export to Excel and run it through a web service as part of the check-in process. http://ayende.com/3289/thoughts-about-building-your-own-source-control#comment10http://ayende.com/3289/thoughts-about-building-your-own-source-control#comment10Thu, 01 May 2008 20:55:59 GMTDan, I may never recover from this suggestion http://ayende.com/3289/thoughts-about-building-your-own-source-control#comment9http://ayende.com/3289/thoughts-about-building-your-own-source-control#comment9Thu, 01 May 2008 08:58:00 GMT..or on top of MS Mesh, and itegrate it into sharepoint and then use WCF. Oh and be sure to use SSIS at some point , just to top it all off. 94640d74-ea07-42d2-9c8c-def42488b8e3 http://ayende.com/3289/thoughts-about-building-your-own-source-control#comment8http://ayende.com/3289/thoughts-about-building-your-own-source-control#comment8Thu, 01 May 2008 08:51:34 GMTHmm... I wonder if anyone ever thought of building a SCM on top of Microsoft's new FeedSync protocol? http://ayende.com/3289/thoughts-about-building-your-own-source-control#comment7http://ayende.com/3289/thoughts-about-building-your-own-source-control#comment7Wed, 30 Apr 2008 10:59:47 GMTHmm, crap. :) I have just begun writing my own after giving up on finding one that does things the way I want it to. As christian says, Git lacks decent Windows support and requires manual db management. Mercurial and Bazaar each have at least one feature the other doesn't and I want both. Trying to build either one from source to extend them failed miserably after I spent two days trying to build Python from source so it would accept extensions compiled in VS 2008. That's open source dependency hell for you. Perforce has served me well for almost ten years, but its lack of good move/rename functionality as well as being cumbersome when it comes to branching is beginning to get on my nerves. It's got to go. Subversion is not an option, its only upside is that it's free, everything else annoys me. ClearCase is too expensive, too slow, too big and has too much legacy to be a real option. BitKeeper looks nice, but the licensing model and license agreement, as well as the available documentation and the general attitude of the company puts me off. AccuRev seem to have gotten the back-end right, but their GUI sucks eggs when you actually try to work in it. And there's a bunch of other commercial alternatives that all lack in features or force me to work in ways I don't like. So, even if it takes forever, I'm going to write my own. And I'll use Rhino.Mocks with xUnit.Net to test it. :) http://ayende.com/3289/thoughts-about-building-your-own-source-control#comment6http://ayende.com/3289/thoughts-about-building-your-own-source-control#comment6Wed, 30 Apr 2008 09:12:54 GMT"Distributed SCM can be handled on top of centralized SCM." First thing I thought of: Git. First comment on blog post: about Git. As much as I use and like Subversion, I do believe that if the client tools were there for Git like they are for svn, Git would soon surpass it. Since you have so much experience now with SVN now, why not go all out and help out Toravalds with a Git implementation that rivals TortoiseSVN. RhinoGit... got a good ring to it! You could also holler "Rhino! Git!" while making commits in Rhino Tools. Shane http://ayende.com/3289/thoughts-about-building-your-own-source-control#comment5http://ayende.com/3289/thoughts-about-building-your-own-source-control#comment5Wed, 30 Apr 2008 01:37:28 GMTSweet! Ayende announces Rhino.SCM! I know I'm not alone when I say that I look eagerly to your estimated end-of-May beta release date. http://ayende.com/3289/thoughts-about-building-your-own-source-control#comment4http://ayende.com/3289/thoughts-about-building-your-own-source-control#comment4Wed, 30 Apr 2008 01:07:29 GMTYep, Git is good but their support for Windows Plataforms still sucky, I prefer myself Mercurial. http://ayende.com/3289/thoughts-about-building-your-own-source-control#comment3http://ayende.com/3289/thoughts-about-building-your-own-source-control#comment3Wed, 30 Apr 2008 00:54:10 GMTFor some reason, I feel very strongly that I should not write my own source control. http://ayende.com/3289/thoughts-about-building-your-own-source-control#comment2http://ayende.com/3289/thoughts-about-building-your-own-source-control#comment2Wed, 30 Apr 2008 00:51:22 GMTCurrently, my preferred SCM is Git. I've used the following SCM's: CVS - Just horrible SVN - Still use it day by day because I have to. It is still ok. Team System - To heavy and quite brittle. Source Safe - No thanks.... In short Git is a distributed SCM that makes tasks like branch & merging extremely easy. You also have features like stash and what is nice, is that you can run Git locally using an remote SVN repo, while the rest of the team is totally oblivious about this fact. When you first look at Git, the whole distributed without a single main repo (ala svn style), just sounds weird. But once you start using Git, you very quickly realize what an awesome SCM it is. When I can share my branch of the code with your git repo while the remote (let's call it main repo) has the official branch. You can then merge my branch into your branch easily and then rebase your branch with the official main branch. Or you can fork the main branch and take it in a completely separate direction. Anyways, as you can see there is so much you can do. And Git makes tasks you would normally not attempt likely, as easy as saying cheese... (if you know git of course) There is multiple good sources of information on the web about Git. (Google Video of Linus, PeepCode, etc.) http://ayende.com/3289/thoughts-about-building-your-own-source-control#comment1http://ayende.com/3289/thoughts-about-building-your-own-source-control#comment1Wed, 30 Apr 2008 00:39:36 GMT