﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Daniel commented on Distributed Source Control</title><description>I respect Git a lot since it's a DVCS but I don't know if I've missed something here. Why Git over Bzr? 
  
  
Bzr seems to be a lot more friendly on windows. I've seen no VS integration yet but TortoiseBzr does most of the things and it also has a more stable renaming capability than Git.
  
  
Yes, Git is faster than Bzr but IMHO userfriendlyness is more important. 
</description><link>http://ayende.com/4216/distributed-source-control#comment15</link><guid>http://ayende.com/4216/distributed-source-control#comment15</guid><pubDate>Tue, 27 Oct 2009 14:26:52 GMT</pubDate></item><item><title>John &amp;quot;Z-Bo&amp;quot; Zabroski commented on Distributed Source Control</title><description>The collaboration features are indeed between yourself and yourself.
  
  
And that's a huge feature.
  
  
Yourself today is not yourself yesterday.
  
  
Yourself when your hard drive is crashing is not yourself when you are writing code.  And guess what all you need to do to verify your repository is to make sure it matches the hash you recorded at a particular release.
</description><link>http://ayende.com/4216/distributed-source-control#comment14</link><guid>http://ayende.com/4216/distributed-source-control#comment14</guid><pubDate>Fri, 02 Oct 2009 23:24:43 GMT</pubDate></item><item><title>Kornelije Sajler commented on Distributed Source Control</title><description>Instead of TortoiseGit I found 
[Git Extensions](http://gitextensions.sourceforge.net) a lot more useful and it integrates nice with Visual Studio. Git Extensions are not as pretty as ViualSVN  but very simple and powerful, jut like Git.
</description><link>http://ayende.com/4216/distributed-source-control#comment13</link><guid>http://ayende.com/4216/distributed-source-control#comment13</guid><pubDate>Tue, 29 Sep 2009 01:21:22 GMT</pubDate></item><item><title>Barry Dahlberg commented on Distributed Source Control</title><description>"But what is client side caching? All the repository? If so, you are in DVCS."
  
  
I guess that helps clarify exactly what a DVCS is for me then!  I know git is so much more than that but I'm mostly a one man team so the collabortaion features are between me myself and I.
</description><link>http://ayende.com/4216/distributed-source-control#comment12</link><guid>http://ayende.com/4216/distributed-source-control#comment12</guid><pubDate>Mon, 28 Sep 2009 21:33:18 GMT</pubDate></item><item><title>Stephen commented on Distributed Source Control</title><description>Oh wow, svn folder hell- can't count how many times I've had to piss around making svn happy.. other than that I've not had THAT many issues with it.
</description><link>http://ayende.com/4216/distributed-source-control#comment11</link><guid>http://ayende.com/4216/distributed-source-control#comment11</guid><pubDate>Mon, 28 Sep 2009 19:00:01 GMT</pubDate></item><item><title>josh commented on Distributed Source Control</title><description>what's also cool about git.. If you have 2 remotes with differing source, you can checkout the clone of that remote as if it was the local copy.  
  
  
Try it.. Go fork a project on github. clone your fork, and add the original as a remote "&gt;git remote add ..." Then make a change to your local, and run "git checkout [remote-name]".  You'll see the code without your change, and you can switch back to your local master to have your change back.
  
  
pretty cool if you ask me.
  
  
</description><link>http://ayende.com/4216/distributed-source-control#comment10</link><guid>http://ayende.com/4216/distributed-source-control#comment10</guid><pubDate>Mon, 28 Sep 2009 17:29:18 GMT</pubDate></item><item><title>Ayende Rahien commented on Distributed Source Control</title><description>Ryan,
  
Oh, I still want everything up there, I am moving between machines so much that I _need_ to maintain stuff out there, otherwise I am facing big sync issues
</description><link>http://ayende.com/4216/distributed-source-control#comment9</link><guid>http://ayende.com/4216/distributed-source-control#comment9</guid><pubDate>Mon, 28 Sep 2009 17:13:54 GMT</pubDate></item><item><title>Ryan Cromwell commented on Distributed Source Control</title><description>Is that the sound of the "everything on the intertubes" pendulum creaking back in the other direction?
</description><link>http://ayende.com/4216/distributed-source-control#comment8</link><guid>http://ayende.com/4216/distributed-source-control#comment8</guid><pubDate>Mon, 28 Sep 2009 14:25:40 GMT</pubDate></item><item><title>Josh Schwartzberg commented on Distributed Source Control</title><description>You should check out Accurev when you do need a centralized system, it's really fast and lets you commit to your own "workspace".
</description><link>http://ayende.com/4216/distributed-source-control#comment7</link><guid>http://ayende.com/4216/distributed-source-control#comment7</guid><pubDate>Mon, 28 Sep 2009 11:57:35 GMT</pubDate></item><item><title>Dmitriy Nagirnyak commented on Distributed Source Control</title><description>Yes, I saw the TortoiseGIT. I also heard it has lots of issues, not sure about that though.
  
  
But still there is not anything like AnkhSVN/VisualSVN. I find them very useful working in Visual Studio. It saves a lot of time by keeping track of actions I do with files.
  
  
Additionally it seems a bit problematic to host GIT on Windows.
  
  
I just don't really get the right feeling about GIT and not sure how I can gain one...
</description><link>http://ayende.com/4216/distributed-source-control#comment6</link><guid>http://ayende.com/4216/distributed-source-control#comment6</guid><pubDate>Mon, 28 Sep 2009 11:55:10 GMT</pubDate></item><item><title>Tobin Harris commented on Distributed Source Control</title><description>I actually much prefer Git for use as a single developer. Creating a local repository on a local or network drive is incredibly simple, and if I want to distribute that repository to a remote server or another person it's also very easy. I even use Git for 1-hour throw away projects just for useful rollback and logging :)
  
  
I don't recall SVN being so simple, mainly because you need more tools - one set of tools for repo admin and another for repo usage.
</description><link>http://ayende.com/4216/distributed-source-control#comment5</link><guid>http://ayende.com/4216/distributed-source-control#comment5</guid><pubDate>Mon, 28 Sep 2009 11:43:21 GMT</pubDate></item><item><title>Ayende Rahien commented on Distributed Source Control</title><description>Dmitriy,
  
There are good tooling for Git. TortoiseGit gives you a very similar experience, for example.
  
And no, there is still the high cost of communication to the server, even for a lone developer.
</description><link>http://ayende.com/4216/distributed-source-control#comment4</link><guid>http://ayende.com/4216/distributed-source-control#comment4</guid><pubDate>Mon, 28 Sep 2009 11:16:10 GMT</pubDate></item><item><title>Dmitriy Nagirnyak commented on Distributed Source Control</title><description>What about tooling? SVN has great tool-set main of them are AnhSVN and TurtoiseSVN.
  
I do not see mature tooling for Git on Windows.
  
  
Also I still think SVN is best suited for a small team (or even for single developer). Can you agree on this?
</description><link>http://ayende.com/4216/distributed-source-control#comment3</link><guid>http://ayende.com/4216/distributed-source-control#comment3</guid><pubDate>Mon, 28 Sep 2009 11:09:41 GMT</pubDate></item><item><title>Ayende Rahien commented on Distributed Source Control</title><description>Barry,
  
.svn folders _are_ annoying, yes.
  
And I like the way Git tracks renames much better, yes.
  
But what is client side caching? All the repository? If so, you are in DVCS.
  
If not, you are going to hit the cache limits and fall back to the same bad experience.
  
I did a lot of SVN Caching when I worked on SvnBridge, it is a _tough_ problem.
  
  
And it doesn't help for fast commits
</description><link>http://ayende.com/4216/distributed-source-control#comment2</link><guid>http://ayende.com/4216/distributed-source-control#comment2</guid><pubDate>Mon, 28 Sep 2009 00:33:12 GMT</pubDate></item><item><title>Barry Dahlberg commented on Distributed Source Control</title><description>Other than fast commits, wouldn't something like SVN with the addition of sensible client side caching have much the same effect?
  
  
For me one of the biggest wins is getting rid of all those .svn folders scattered through my project causing no end of trouble when renaming or copying folders.
</description><link>http://ayende.com/4216/distributed-source-control#comment1</link><guid>http://ayende.com/4216/distributed-source-control#comment1</guid><pubDate>Mon, 28 Sep 2009 00:27:44 GMT</pubDate></item></channel></rss>