[Vm-dev] a Cog branch

[Igor Stasenko]

Does Mercurial provides an infrastructure like github?
I mean, if it doesn't , then it is nothing better than svn (the fact
that i could have a full copy
of repository locally doesn't much matters).
I really don't care what version control system used as a backend, i
care about infrastructure around it.
On a github its ultimately easy to get started and make own fork(s) of
existing projects,
and moreover, all such things are tracked, not just sources.
So, users could see how much forks there, and could navigate through
them etc etc.
The fancy & clever diff/merge etc things is cool, but used seldom,
because 99% of times you just doing
edit/commit.

On 25 June 2010 02:46, Josh Gargus <josh at schwa.ca> wrote:
>
> +1 Mercurial, -1 Git.
> Cheers,
> Josh
>
>
> On Jun 24, 2010, at 3:43 PM, Eliot Miranda wrote:
>
>
> On Thu, Jun 24, 2010 at 8:13 AM, Igor Stasenko <siguctua at gmail.com> wrote:
>>
>> Eliot, how about using github for it?
>
> I think that's great for the whole Squeak VM not just Cog.  I'm not doing this now because I think Cog should live with the rest of the Squeak VM.  Let's start a separate discussion on whether we should move http://squeakvm.org/svn/squeak to github, or at least to git with a home on machines we control..
>
>>
>> It would be much convenient for use, since it supports branching and
>> no need for someone to be added to 'official' list of contributors in
>> order to push own
>> patches.
>> Anyone could make own fork at any time, and at any time, a core
>> developer could backport the changes
>> into official repository.
>> I think github model is very good for community development. Then i,
>> for instance, could
>> push my own changes into my branch, and it will be easy to track,
>> exchange and port the code between
>> forks and official repository.
>
> Agreed.  Git and/or Mercurial is much better than svn.
> best
> Eliot
>>
>> On 23 June 2010 21:48, Eliot Miranda <eliot.miranda at gmail.com> wrote:
>> >
>> > Hi All,
>> >     I need to be able to push fixes to Cog into general circulation and for this I'd like to maintain a Cog branch in the Subversion tree.  But how do I get permission and/or credentials?  What's the process to add me to those allowed to write to the repository? Or is there simply a secret username and password that's told to a few?  If the later can some kind soul let me have the password.  I faithfully promise not to abuse the privilege.
>> > best
>> > Eliot
>> >
>>
>>
>>
>> --
>> Best regards,
>> Igor Stasenko AKA sig.
>
>
>
>



-- 
Best regards,
Igor Stasenko AKA sig.