[ECOS] eCos VCS switch

Alex Schuilenburg alexs@ecoscentric.com
Thu Sep 17 14:45:00 GMT 2009

[Apologies to Daniel for the repost - my original email to ecos-discuss
was bounced]

Daniel Néri wrote on 2009-09-17 15:01:
> Alex Schuilenburg <alexs@ecoscentric.com> writes:
>> I cannot speak for these tools, other than to say I have tried to
>> import our internal CVS repository and anoncvs into all three and not
>> one of them worked. git did the worst job, followed by bazaar then
>> mercurial. And yes, I have tried cvs2svn to go via svn as well :-(
> I've been tracking the eCos anoncvs using Mercurial for more than 3
> years. At first I was using Tailor for conversion, but I'm currently
> using the bundled "convert" extension.
> The main problem for me was always the somewhat strange "grafting" of
> the 'net' sub-directory into 'packages' using CVS module magic. I worked
> around that by converting 'net' and 'packages' into separate Mercurial
> repositories which I then merge (i.e. "hg merge -f") to make my own
> working repository.
Unsurprisingly, this was also the first problem I encountered using the
hg convert extension.

The next problem was exactly how faithfully you wanted to make the
conversion.  Unfortunately, the hg convert's version of cvsps is pretty
basic and will fail on all but the simplest of repositories.  Hence I
had to switch, eventually, the the 2.2beta of cvsps proper. Also, use
cvs admin in earnest once and you can kiss goodbye any chances of a
faithful reproduction without manual fixes. 

In addition, the early version of cvs used in the anoncvs repository
never handled files being introduced on a branch properly, so when you
checkout against specific dates, you get unexpected results on the trunk :-(

> A switch of the public CVS repository to Mercurial would be a major
> improvement.
Agreed.  My initial findings are also that mercurial is the preferred
solution.  It is not as powerful as git, or even as fast, but it is
easier to work with and has better documentation.  Besides, the speed
differences were not that great (just google and you can get 100's of
independent comparisons), and I would rather not trip over the rope. 
IMHO, nothing we do in eCos development warrants the use of git over
that of mercurial (or bazaar).  90% of the features of git probably
would not be used, even once you figured them out ;-)

-- 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

More information about the Ecos-discuss mailing list