public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: daniel.neri@sigicom.com (Daniel Néri)
To: ecos-discuss@sources.redhat.com
Subject: [ECOS]  Re: eCos VCS switch
Date: Fri, 18 Sep 2009 12:20:00 -0000	[thread overview]
Message-ID: <873a6kzboy.fsf@quadra.hq.sigicom.net> (raw)
In-Reply-To: <4AB37791.7090601@ecoscentric.com>

Alex Schuilenburg <alexs@ecoscentric.com> writes:

> My favourite hg extension is forest which allows you to create a single
> repository consisting of several other repositories, kind of like CVS
> modules.

Note that Mercurial version 1.3 includes an experimental subrepository
core feature. This might eventually make the forest extension obsolete.

  http://mercurial.selenic.com/wiki/subrepos

> In other words, you can work with all the repositories, or just with
> subsets. This means that multiple changes can be push/pulled into/from
> multiple repositories, using a single standard hg push/pull commands,
> as well as all the usual hg commands and functionality. I have not
> heard of equivalent functionality in git ;-)

Git has submodules, which is a similar feature.


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

      reply	other threads:[~2009-09-18 12:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17 14:45 [ECOS] " Alex Schuilenburg
2009-09-17 21:15 ` Jonathan Larmour
2009-09-17 22:56   ` Alex Schuilenburg
2009-09-18 10:08   ` [ECOS] " Sergei Organov
2009-09-18 10:41   ` Sergei Organov
2009-09-18 12:05     ` Alex Schuilenburg
2009-09-18 12:20       ` Daniel Néri [this message]

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=873a6kzboy.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).