[Vm-dev] a Cog branch
stephane.ducasse at gmail.com
Fri Jun 25 22:18:06 UTC 2010
But andreas if people cannot easily post their contributions then they will leave, or they will fork anyway.
This is really simple to clone a svn repository.
We were planning to have a github dedicated to vm contributions so that people investing time to get a better
make for windows for example can contribute and like that we have no stress that you get busy or not.
The VM maintainer can decide if they want it or not. They can cherry pick the changes.
But we can also access it and use it and contribute to it.
This is like the immutability it even if it is not introduced then having an entry point to find the
code is an advantage.
As igor said git is a tool and you can build a process around it.
> On 6/25/2010 1:59 PM, Bert Freudenberg wrote:
>> I really cannot understand your objection.
> Yes, I'm obviously doing a bad job formulating my concern :-)
> The concern isn't about the utilization of a DVCS. The concern is about people saying "hurray, now we can finally fork". If we're in a situation that people feel that way, then we're doing something wrong and it has nothing to do with the use of a DVCS.
> So everyone here explaining to me how great it is to fork is doing nothing but deepening my concern that we have a real problem and that the only outcome of a switch to a DVCS is that we'll end up in a multitude of incompatible forks. Which is what I'm trying to avoid.
> - Andreas
More information about the Vm-dev