[ECOS] What's the process on switching version control system for eCos?

Jonathan Larmour jifl@jifvik.org
Fri Sep 25 00:33:00 GMT 2009

Alex Schuilenburg wrote:
> Bart Veer wrote on 2009-09-22 15:34:
>>  b) how much history can we expect to lose, irrespective of the
>>     amount of effort put in?
> Only what cvsps misses, or rather, does not know what to do with (google
> CVSPS_NO_BRANCH for details). Those files or changes are basically
> orphaned.  However, I will send a list of the files along with their
> revisions to the maintainers and you can decide what to do with them.

Frankly I wouldn't worry about it to that level - if that level of digging 
is required to find out past history, the best thing to do is to look 
directly at the old CVS repository.

Those orphaned changes are probably the result of "cvs admin" hacks and so 
on. In which case they were probably orphaned for a reason.

>>So, a suggestion that e.g. eCos should switch over to git because it
>>is already in use on other projects is unlikely to get much attention
>>from the maintainers. A serious offer to do the hard work will get
>>much more attention, especially if it is backed up with experimental
>>data and explanations of why some of the problems with cvs are just
>>too hard to work around.
> My offer in my previous email is serious.  Little skin off my nose and
> most CPU cycles are free.  I have already developed my script in-house
> for an internal conversion and so we can evaluate the different DRCS
> systems.  What the maintainers or community choose to do with the repo
> is up to them, but moving an hg repo to sourceware will be has hard as
> "hg clone http://hg.ecoscentric.com/ecos", while converting it to git or
> bzr a matter of exporting the patchsets (this time without error) from
> hg after cloning it and importing them.

I for one would like to take you up on that! Even if the choice isn't hg 
that effort would be useful and not wasted.

--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine

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