Forest? Branches? And other beginner questions...

[Marcin Kasperski]

> > (question 1)
> >  From the docs I've read I got the feeling, that I should
> > use 'many repositories' (= create separate mercury directory
> > for every program, library, documentation, whatever I track)
> > - so the tagged, pulled, pushed item is not made of a few
> > independent entities.  (...)
>
> I don't think the advice is necessarily to have separate
> repositories for each program, library, document, etc. If
> there is a set of related stuff, say some libraries and a set
> of programs that use those libraries, along with
> documentation, then it would make sense for them all to reside
> in the same repository. 

Unless I missed something, it is impossible to tag part of the 
repository. So, if - say - some library and some program need to 
be tagged separately, then they must live in separate 
repositories. 

Do I miss something?

> I don't know anything about the Forest extension. Looking at
> the extension page
>
> http://www.selenic.com/mercurial/wiki/index.cgi/ForestExtensio
>n
>
> it sort of makes sense, but I'm having trouble imagining the
> circumstances under which it would be useful.

Let's start from small and simple things. Imagine we have 
configuration of - say - 10 libraries and 3 applications, and 
small team which needs all of them in most cases. It is nice to 
be able to checkout everything by one command, pull/push 
everything via one command, etc.

It is in fact a kind of workaround for the lack of sub-tree 
handling.


Thanks for your comments.