[ECOS] Re: What's the process on switching version control system for eCos?
Tue Sep 22 15:57:00 GMT 2009
Alex Schuilenburg <email@example.com> writes:
> Sergei Organov wrote on 2009-09-22 15:59:
>> Ãyvind Harboe <firstname.lastname@example.org> writes:
>> IMHO, eCos is not that big to worry about the size of the repository,
>> provided huge binary images are not put into the repository.
> Seen ecos-images?!?!?
That's what I meant. They shouldn't be there in the eCos source code
repository, be it CVS or anything else. Someone who needs them (though I
doubt anybody does) should be able to download them separately.
> My choice of mercurial is immaterial as to the final choice of DRCS
> since it can easily be exported to git or bzr if that is the final
> chosen DRCS.
Yes, sure, so the tool that works best for conversion, or those one you
are most comfortable with is preferred.
> Also, I will be killing the images (some 98MB) from the repo, but will
> preserve it as a separate repo in case anyone is insane enough to want
> them. FYI, they were various binary images of gdb stubs or redboot for
> rom or ram or romram startup for various platforms, most of which are
> now obsolete. While a nice idea, the practice of keeping the images
> updated for new platforms was not followed by the maintainers since we
> left planet Red Hat. You can always merge the repositories if you want
> a closer reproduction of CVS.
Yes, this is very reasonable decision.
> I say closer because, rather than doing a faithful CVS convertion, I am
> fixing problems like files not actually being tagged as part of a
> release (i.e cvs co -r <tag>) despite existing in the repo on a branch
> when the tag was made and being shipped with the release and others
> previously mentions. I have had to become a CVS expert to detect and
> fix most of these problems and now HATE CVS with such a passion you
> would not believe.
I've tried to convert a few CVS repositories to git, so I do know what
you are talking about. You have my sympathies!
> I intend to make this hg repo available to everyone from one of our
> servers, and will update it at least weekly with updates from anoncvs
> (maybe daily, depends on the load) until a DRCS choice has been made and
> is live on sourceware. At least until then some folks have an
> alternative download method and can better prepare
> patchsets/contributions. Actual delivery date depends on my "real work"
> workload. Talking about which...
Oh, you even hope to have incremental updates! Very nice indeed!
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