[Click] distributed source control

[Eddie Kohler]

Hey Bart,

So the Git system will be just as easy as anonymous CVS, for the basic 
anonymous CVS operations.  Where previously you typed "cvs co", you will now 
type "git clone".  Where previously you typed "cvs up", you will now type "git 
pull".  Where previously you typed "cvs diff", you will now type "git diff".

As Brendan points out, one can use a distributed system in exactly the same 
way you currently use the more centralized system.  Click's home repository 
will still be the center of development (for as long as it is maintained). 
The advantage is it will hopefully get easier for people to test out their 
ideas, and for me to integrate those ideas.

We'll see how this goes.  One advantage of git (although hg might have it too) 
is that git can serve the CVS protocol.  So you can easily continue using 
anonymous CVS as if nothing had changed.

Thanks,
Eddie


Bart Braem wrote:
> On Thursday 05 July 2007 19:46, Eddie Kohler wrote:
>> I would like to move away from Click's current anonymous CVS based
>> development model to a distributed source control system.  This would
>> let people maintain public branches of their own.  I am leaning towards
>> "git", the tool originally developed for Linux.
>>
>> http://git.or.cz/
>>
>> Any complaints or comments?  Speak now!
> 
> Hi Eddie,
> 
> Can I ask why you want a distributed system? 
> I really like the idea of moving away from CVS, the advantages of using it are 
> starting to fade quickly, compared to other solutions available today. 
> But I don't like the idea of using a distributed system. Of course the 
> advantage is that separate people can use their own repositories. But then 
> the integration with the Click "core" will get harder when API changes are 
> made. Repository owners will have to indicate compatible Click versions, I'd 
> think.
> But I might be too old-fashioned here, does anyone have experience with 
> synchronization of source repositories? Does this work, is it hard to keep up 
> with the core repository?
> Currently for some internal projects we are using SVN and combined with 
> TortoiseSVN even newbies can perfectly use it. But perhaps access permissions 
> will be harder to manage than in distributed systems.
> 
> A second remark: please consider something more usable than git. To me it 
> seemed really hard to use, last time I tried to use it. 
> I do not know whether mercurial or svk or ... are more userfriendly, but I 
> feel that we should avoid building a barrier for people to use the latest and 
> greatest Click release.
> 
> I'd like to join the other in thanking you for Click, it really helps me!
> 
> Just my 2 eurocents of course,
> Bart
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> click mailing list
> click at amsterdam.lcs.mit.edu
> https://amsterdam.lcs.mit.edu/mailman/listinfo/click