Status of adding "overlay repositories" to standard Mercurial?

[Stuart Marks]

Giorgos Keramidas wrote:
> This is a very interesting concept, because AFAICT it makes Mercurial
> match very closely the behavior of Sun's Teamware system.  Working with
> a ``workspace-tree'' is then much much cheaper in disk space than
> keeping the entire metadata in every clone.

I'm not sure which aspect of overlay repositories matches Sun's old Teamware 
system. As far as I know Teamware makes copies of all history and metadata 
(SCCS files) for every workspace. (In other respects, though, Mercurial is 
already similar to Teamware, irrespective of overlay repositories.)

I do agree that overlay repositories are an interesting concept, and I'd like 
to learn more about them.

s'marks