Inter-Repository work.... (new to mercurial)

[Thomas Lehmann]

> That's the basic operation.  The mirror operation is
>
>   cd \MercurialRepository
>   hg push ..\XmlBasedGuiDesign
>
> Once you understand what's going on there, you're ready to start
> having fun.  ;-)  But in the meantime, stop thinking about files and
> directories and file versions.  Think *changesets*.

That it's.
This means I would have to separate EACH small project into separate
repositories to avoid any mixes.
The basic advantage of the commit has been that I do not have to
"checkin"
each individual file by hand as in SCCS. But on the other side the
danger to
introduce dependencies is to high then. This is an issue you won't
fail in
subversion; when I'm saying: give my this path, I get it. A version is
not to
separate structuring like files and folder are doing.

Your example is working well - of course - but I get simply too much!
If not done (probably I have not been reading correctly) you should
explain
that main difference in the doc.

Nevertheless I will continue using mercurial because I find it
interesting.
I will simply copy by hand (batch/python) each change of one
repository to another
doing a commit then. I will work on the local repository then. The
caveat is
that I will have also to synchronize the local with the bitbucket one.
For a
smaller project as I have it can be done. I wouldn't use this for
large issues.