<br><div class="gmail_quote">On Fri, Jun 25, 2010 at 10:09 AM, Andreas Raab <span dir="ltr"><<a href="mailto:andreas.raab@gmx.de">andreas.raab@gmx.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
On 6/25/2010 1:05 AM, Geoffroy Couprie wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
On Fri, Jun 25, 2010 at 9:53 AM, Andreas Raab<<a href="mailto:andreas.raab@gmx.de" target="_blank">andreas.raab@gmx.de</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
On 6/24/2010 7:16 PM, Igor Stasenko wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
One user could create a project, then others may create forks or<br>
subforks of his project(s)<br>
</blockquote>
<br>
How exactly is this a good thing? I don't want 200 forked Squeak VM<br>
versions; I want one canonical source that people can build from.<br>
<br>
</blockquote>
<br>
Forks can be really useful for people who have to maintain a set of<br>
patches that may not be accepted in the repository (applications<br>
requiring a specific VM configuration, servers, etc).<br>
</blockquote>
<br></div>
Do we have this problem? What patches do you or anyone else have that can or should not be integrated in the main source?<br></blockquote><div><br></div><div>While I was trying to build squeak vm for Pharo with FT2Plugin I had to maintain 3 patches long before they were integrated in squeak vm trunk.</div>
<div><br></div><div>With a DVCS it's easier to make collaborative experimentations, try new things, merge the good ones, see popular patches. </div><div><br></div><div>That doesn't mean there's no official branch anymore. </div>
<div><br></div><div>Cheers,</div><div><br></div><div>Laurent</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Cheers,<br><font color="#888888">
- Andreas</font><div><div></div><div class="h5"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
With the<br>
branching workflows in DVCS, you can still get updates from the main<br>
repository, develop new features in parallel, and maintain your<br>
patches without impacting the rest of the developers.<br>
<br>
With SVN, if you don't have commit access, you only have two<br>
possibilities: store a lot of patches, and reapply them by hand at<br>
each update, or use a dirty trick like git-svn. I'm using git-svn<br>
right now: it is great to be able to commit locally, but it's a bit<br>
heavy to use.<br>
<br>
</blockquote>
</div></div></blockquote></div><br>