Re: [Kde-scm-interest] distributed source control status

2008-10-26 Thread Thomas Zander
On Monday 27. October 2008 02:18:43 Thomas Capricelli wrote: > Other projects using mercurial (opensolaris, xine, audacious..) do not > seem to find that those two points are showstopper. The most common > pattern is to have a central repository people access with ssh keys > (which is less 'open' t

Re: [Kde-scm-interest] distributed source control status

2008-10-26 Thread Thomas Capricelli
On Monday 13 October 2008 06:41:49 Boyd Stephen Smith Jr. wrote: > I'd also mention that Thiago and others have already put quite some work > into getting Git ready to be KDE's new VCS [see Thomas' earlier email > ITT), and it might be easier to built on that work (even if it's with > another VCS)

Re: [Kde-scm-interest] distributed source control status

2008-10-12 Thread Boyd Stephen Smith Jr.
On Sunday 12 October 2008, Paul Hummer <[EMAIL PROTECTED]> wrote about 'Re: [Kde-scm-interest] distributed source control status': >What do you mean by "serious?" Bazaar can easily handle the distributed >workflow of KDE. In my extremely limited experience with b

Re: [Kde-scm-interest] distributed source control status

2008-10-12 Thread Paul Hummer
Thomas Capricelli wrote: > > > On venerdì 10 ottobre 2008, Boyd Stephen Smith Jr. wrote: >>> The only other option is mercurial I think. >> I'm fairly sure the project is considering any DVCS. > > Sure, but i meant that I can't see any other serious contender. > > What do you mean by "ser

Re: [Kde-scm-interest] distributed source control status

2008-10-10 Thread Evgeniy Ivanov
Boyd Stephen Smith Jr. wrote: > On Thursday 09 October 2008, Thomas Capricelli <[EMAIL PROTECTED]> > wrote about 'Re: [Kde-scm-interest] distributed source control status': >> On venerdì 10 ottobre 2008, Boyd Stephen Smith Jr. wrote: >>> we need something to r

Re: [Kde-scm-interest] distributed source control status

2008-10-09 Thread Thomas Zander
On Friday 10. October 2008 01:53:06 Thomas Capricelli wrote: > Hello, > > There were some discussions in august about studying the use of a > distributed source control for KDE. My understanding is that some tests > were made using git, and it was more or less decided that at some time, > kde

Re: [Kde-scm-interest] distributed source control status

2008-10-09 Thread Boyd Stephen Smith Jr.
On Thursday 09 October 2008, Thomas Capricelli <[EMAIL PROTECTED]> wrote about 'Re: [Kde-scm-interest] distributed source control status': >On venerdì 10 ottobre 2008, Boyd Stephen Smith Jr. wrote: >> we need something to replace kdesvn, and the > >This one is easy

Re: [Kde-scm-interest] distributed source control status

2008-10-09 Thread Thomas Capricelli
On venerdì 10 ottobre 2008, Boyd Stephen Smith Jr. wrote: > > The only other option is mercurial I think. > > I'm fairly sure the project is considering any DVCS. Sure, but i meant that I can't see any other serious contender. > That's what any DVCS needs to be seriously considered. Some

Re: [Kde-scm-interest] distributed source control status

2008-10-09 Thread Boyd Stephen Smith Jr.
On Thursday 09 October 2008, Thomas Capricelli <[EMAIL PROTECTED]> wrote about '[Kde-scm-interest] distributed source control status': > There were some discussions in august about studying the use of a > distributed source control for KDE. My understanding is that

[Kde-scm-interest] distributed source control status

2008-10-09 Thread Thomas Capricelli
Hello, There were some discussions in august about studying the use of a distributed source control for KDE. My understanding is that some tests were made using git, and it was more or less decided that at some time, kde would migrate to git. Although I'm not sure how 'final' this de