I think there's a misconception here. The fact that DVCS makes you easy to branch doesn't mean that there will be a lot of disconnected incompatible forks thrown out there.<div><br></div><div> Branches in DVCS are not the same as branches in SVN, they are not used the same way. i.e. in GIT, you create a branch each time you start working in a new feature, no matter if it is big or small. That helps you to keep your changes isolated from the mainline. Then, you commit your changes into your branch. After some commits, when the code is ready, you merge them to the mainline again.</div>
<div><br></div><div> The are many things that are really really really nice thing about DVCS. One of them is that it helps A LOT in merging the changes back. Besides, you can have your changes in a really tidy way, because you go on commiting all the time, even if your code is not ready to be merged to the mainline, you do it locally. When the code is ready, the DVCS will make it very easy to merge it back to the mainline and to do it without loosing the history of commits. At last, with infraestructure like github (or others) you can make your own branch public so that other people can collaborate with you, and the result is that your branches end up getting incorporated into the mainline quicker and are never lost.<br>
<br></div><div>Of course, I support the idea of DVCS, be it any of them (I think they are all compatible anyway, because they share their distributed nature).</div><div><br></div><div>Regards,</div><div> Javier.</div>
<div><br><div class="gmail_quote">On Fri, Jun 25, 2010 at 10:26 AM, laurent laffont <span dir="ltr"><<a href="mailto:laurent.laffont@gmail.com">laurent.laffont@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br><br><br><div class="gmail_quote">On Fri, Jun 25, 2010 at 2:14 PM, David T. Lewis <span dir="ltr"><<a href="mailto:lewis@mail.msen.com" target="_blank">lewis@mail.msen.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><br>
On Fri, Jun 25, 2010 at 11:18:19AM +0200, Bert Freudenberg wrote:<br>
><br>
> So I'm strongly in favor of switching to a DCVS. I personally only ever<br>
> used git, but since hg supposedly has better x-platform support that<br>
> would be fine too (the Windows devs should speak up). Wouldn't be<br>
> opposed to bzr either.<br>
><br>
<br>
</div>I don't know if this is a good idea or not, but I have to say that<br>
right now would be a poor time to consider major changes to the<br>
infrastructure unless there is a *truly* compelling reason to<br>
do so. </blockquote><div><br></div><div><br></div><div>I think the opposite :) It's a wonderful opportunity to learn. When I started working on the Linux kernel, I've learned a lot because all patches go through the Linux Kernel Mailing List (thanks to Git), discussed, reviewed, integrated in experimental branches and finally in official one.</div>
<div><br></div><div>A real force of Git infrastructure is to bring visibility. Cog is here, let's learn, play and contribute easily.</div><div><br></div><div>Cheers,</div><div><br></div><div>Laurent</div><div><br></div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The reason is managing change overall - the Cog development<br>
represents a huge opportunity, but it also implies a lot of new<br>
things to understand and integrate, and new work to be done by<br>
folks who will need to understand the changes. Performing a<br>
simultanious migration to new version control and build processes<br>
would likely lead to delays and disruption in the more important<br>
objective of making progress on the VM.<br>
<br>
I suggest that we focus on successful integration of Cog this year,<br>
and consider moving to some new version control infrastructure at<br>
a time when we are sailing on calmer waters.<br>
<br>
Dave<br>
<br>
</blockquote></div><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Javier Pimás<br>Ciudad de Buenos Aires<br>
</div>