Alternative to "forests"

[Kelly O'Hair]

Very interesting. I like it.

How about a "description = words" field to describe what each repo is?

One of the issues I'm having with the OpenJDK forest is creating a
kind of 'forest tag' to describe the state of the entire forest with
one file or simple set of changeset ids.
So something like a 'hg fsnap' ('hg module --dumpstate > state'?) would be
helpful, and then being able to re-create a forest later in time
with a 'hg clone -M state'???

Ultimately I would like to bake this information into the built product so
that at some later time, you could re-create the exact sources used to
create a product, at anytime, easily and quickly.
Dealing with one repository and one product is easy, these bigger puppies
are a little more complicated. ;^)

-kto

Bryan O'Sullivan wrote:
> Benjamin Smedberg wrote:
> 
>> Thoughts?
> 
> Please chew over this:
> 
> http://www.selenic.com/mercurial/wiki/index.cgi/NestedRepositories
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial