<div class="gmail_quote">On Thu, Jul 10, 2008 at 11:20 AM, Jeffrey Ollie <<a href="mailto:jeff@ocjtech.us">jeff@ocjtech.us</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Thu, Jul 10, 2008 at 9:52 AM, Tim Perdue <<a href="mailto:tim06@perdue.net">tim06@perdue.net</a>> wrote:<br>
><br>
> but it's not for the average run-of-the-mill developer shop IMHO.<br>
<br>
</div>I beg to differ. I work on a number of projects and most of them have<br>
only a few developers, and several have only one (me). I find Git<br>
extremely useful in all of these cases. Sure, I may not be using the<br>
"full" power of Git but there's more to git than it's distributedness.<br>
In fact, one of the best features of Git is its blazing fast speed.<br>
It doesn't sound like taking an operation that takes a couple of<br>
seconds in Mercurial or Bazaar and doing it in sub-second times with<br>
Git would make much of a difference but it does once you get used to<br>
it. There are lots of other reasons why I like Git, but to say that<br>
Git wouldn't be useful in a "average run-of-the-mill developer shop"<br>
is just silly.</blockquote><div><br>Personally I agree with Tim here. Git might be useful however I think that the "normal" VCS system is much more suited to a developer shop model. We have developers, designers, and "production" people all working against common code bases. The Git model just seems to complicate the VC compared to say SVN if you are using it right. I can see how it might be useful in a distributed setup (still a bit wary) but the number of merges & conflicts that Git seems inclined to generate would be a pain in your average shop.<br>
</div></div><br>