From: daniel.neri@sigicom.com (Daniel Néri)
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Re: eCos submodule support
Date: Tue, 20 Oct 2009 07:50:00 -0000 [thread overview]
Message-ID: <87aazmec8a.fsf@quadra.hq.sigicom.net> (raw)
In-Reply-To: <c09652430910191417n584ceed8kdf4f06906f96c91f@mail.gmail.com>
Øyvind Harboe <oyvind.harboe@zylin.com> writes:
> - when various people work on the same project, we don't
> have to write scripts to set up the build environment(e.g.
> extract a specific version of eCos snapshot). It's
> clone + submodule init + submodule update => voila!
>
> At this point I have no idea what happens when
> throwing mercurial into the mix here, but "easy"
> isn't the first word that comes to mind :-)
With hg it's just "clone" and the subrepos are automagically pulled and
updated. How is that harder?
Regards,
Daniel
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2009-10-20 7:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c09652430910191038m6ddd7153gcb6d7616719a72c9@mail.gmail.com>
2009-10-19 21:17 ` [ECOS] " Øyvind Harboe
2009-10-20 7:50 ` Daniel Néri [this message]
2009-10-20 10:47 ` [ECOS] " Øyvind Harboe
2009-10-20 14:45 ` Sergei Organov
2009-10-20 21:37 ` Alex Schuilenburg
2009-10-20 23:19 ` Alex Schuilenburg
2009-10-21 6:47 ` Øyvind Harboe
2009-10-20 14:37 ` [ECOS] " Alex Schuilenburg
2009-10-20 14:50 ` Øyvind Harboe
2009-10-20 19:22 ` Alex Schuilenburg
2009-10-20 19:36 ` Øyvind Harboe
2009-10-21 0:00 ` Jonathan Larmour
2009-10-20 23:55 ` Jonathan Larmour
2009-10-21 1:43 ` Alex Schuilenburg
2009-10-23 8:54 [ECOS] " Alex Schuilenburg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87aazmec8a.fsf@quadra.hq.sigicom.net \
--to=daniel.neri@sigicom.com \
--cc=ecos-discuss@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).