Replacing the forest extension with core functionality

[Benoît Allard]

> Now.  Since you actually use forest, maybe you can answer another
> question or two for me.  What other commands actually need to be able to
> traverse module/forest/whatever boundaries?

What I use on a frequent basis, sorted by order of appearance:
- fsnapshot
- fincoming
- foutgoing
- fpull
- fpush
- fstatus (But I agree, it's ugly to read)
- fclone

 >> On the "optional = " config item:  one person's required repo is very
 >> often another's unneeded baggage, so I would treat all modules as
 >> optional (which makes the config item unnecessary).  Use case:  I just
 >> want to look at the history for two specific repos out of the ten
 >> listed; I don't want to download all the related stuff that might be
 >> considered "required" to do a build.
 >
 > I'm not sure a plain "optional" specification cuts it anyway, since it
 > doesn't capture anything but the most pedestrian of needs.  Probably
 > more useful would be a "configuration" notion, as in "get me everything
 > I need to work with the 'server' configuration", then allow a module to
 > be selectable by any of zero or more configurations.

+1 But I'd like to be able to preview what's on the other side, and then 
create my include/exclude list

Benoit
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 4197 bytes
Desc: S/MIME Cryptographic Signature
Url : http://selenic.com/pipermail/mercurial-devel/attachments/20080415/15d4961c/attachment.bin