This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: eCos submodule support
- From: Ãyvind Harboe <oyvind dot harboe at zylin dot com>
- To: eCos Disuss <ecos-discuss at ecos dot sourceware dot org>
- Date: Tue, 20 Oct 2009 12:47:30 +0200
- Subject: [ECOS] Re: eCos submodule support
- References: <c09652430910191038m6ddd7153gcb6d7616719a72c9@mail.gmail.com> <c09652430910191417n584ceed8kdf4f06906f96c91f@mail.gmail.com>
To be a bit more clear:
My assumption is that there is no appreciable difference
between hg/git for the case when *all* modules are
either git/hg.
The problem is with heterogeneous projects.
When working with eCos I've only ever encountered
git, cvs and svn as version controls. CVS very rarely
these days. I'm sure there are eCos relevant projects
that use hg, I just haven't encountered them.
Managing svn as a submodule in git is easy enough.
I have never tried to manage hg as a submodule in git.
So, eCos choosing "the other DVCS" would
make my life harder even if that "other DVCS" is
better.
Does anyone have experience managing non-trivial
hg projects as git submodules?
--
Ãyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss