This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
[Fwd: Re: Re: Switching to using git on eCosForge]
- From: Alex Schuilenburg <alexs at ecoscentric dot com>
- To: eCos Disuss <ecos-discuss at ecos dot sourceware dot org>
- Date: Thu, 17 Sep 2009 15:43:20 +0100
- Subject: [ECOS] [Fwd: Re: [ECOS] Re: Switching to using git on eCosForge]
[Apologies to Sergei for the repost - my original email to ecos-discuss
was bounced]
Sergei Organov wrote on 2009-09-17 14:31:
> Alex Schuilenburg <alexs@ecoscentric.com> writes:
>
>> Ãyvind Harboe wrote on 2009-09-17 11:52:
>>
>>> Does anyone know a reason not to switch to git for eCosForge?
>>>
>>> My thinking is to use http://repo.or.cz/ to host projects.
>>>
>>> www.ecosforge.net uses a version of subversion that is getting
>>> a bit long in the tooth (1.4) and I'm just wondering if
>>> git isn't a better choice anyway....
>>>
>>> The plan is to leave the current subversion repository as-is and
>>> let migration happen eventually, deleting old repositories(they
>>> are still there in the history) after migration to git.
>>>
>>> The idea is to have one git repository per eCos repository(or
>>> project if you will).
>>>
>>> The first project I would like to switch to git, is nios2ecos.
>>>
>> Why git in particular?
>>
>
> Because it's simply the best? ;-)
>
Define "best" ;-)
Most powerful? Sure!!! Easiest to use? No. Best Windows support? No.
Better documented? No.
>
>> We have started looking at switching to another RCS at eCosCentric as
>> well. In particular I looked at three distributed RCS solutions: git,
>> bazaar and mercurial. While there is no doubt that git is the most
>> powerful of the three solutions and also fastest on linux, it is also
>> the most complex of the three solutions with a very steep initial
>> learning curve, it's support for windows is lacking, and its
>> documentation is sparse and confusing. As a tool for experienced Linux
>> developers, sure, git is the best choice. But for the average eCos
>> developer, I am not convinced.
>>
>
> Did you see this:
>
> <http://code.google.com/p/msysgit/>
>
> (I'm not Windows user, so didn't use it myself).
>
Yup, but when you are playing with a mixture the cygwin tools used by
eCos and those native tools, you get interesting results. See the
msysGit mailing list <http://groups.google.com/group/msysgit>.
> BTW, git has gitcvsserver:
>
> <http://www.kernel.org/pub/software/scm/git/docs/git-cvsserver.html>
>
> so those who are used to CVS and don't wish to learn new tool can
> continue to use their favorite CVS clients.
>
The point is to get away from a broken-by-design system ;-)
-- Alex Schuilenburg
>>>> Visit us at ESC-Boston http://www.embedded.com/esc/boston <<<<
>>>> Sep 22-23 on Stand 226 at Hynes Convention Center, Boston <<<<
**** Visit us at ESC-UK http://www.embedded.co.uk ****
**** Oct 7-8 on Stand 433 at FIVE ISC, Farnborough ****
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss