Status of adding "overlay repositories" to standard Mercurial?

[Giorgos Keramidas]

On 2007-02-26 11:46, Stuart Marks <Stuart.Marks at Sun.COM> wrote:
>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.

I have only used Teamware *very* briefly, so I could be wrong.  What I
was referring to was the ability to not copy the 'data' part of a file
in a child workspace, unless it does have local changes.

At least that's what I remember from my brief encounter with TW.  If
this is wrong, I apologise for the confusion.  Now that I reread the
Teamware User's Guide it seems I was probably confusing this with the
PROTO1, PROTO2, ... build-time hierarchy :-/

> 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.)

Yes, pretty much :)