Re: [Monotone-devel] Re: Problems with _MTN/tmp

[Johan Bolmsjö]

On Thursday 01 June 2006 10.35, Nathaniel Smith wrote:
> On Wed, May 31, 2006 at 10:17:43PM +0100, Joel Crisp wrote:
> > I think that one feature of config specs which hasn't been mentioned yet
> > is 'lazy branching'
> >
> > In other words, I have a personal branch which shadows a team integration
> > branch which shadows the main branch.
> >
> > If I checkout a file which only exists on the main branch, it
> > automatically creates branched versions of that file on the team and
> > personal branches.
> >
> > A rule like (sorry, can't remember the exact syntax and I'm at home atm):
> >
> > * /main/team/personal/CHECKEDOUT
> > * /main/team/LATEST
> > * /main/LATEST
> > * mkbranch /main/team/personal
> >
> > would automatically make a branch on /main/team/personal whenever I check
> > a file out
> >
> > This is some of the magic of config specs ;-)
>
> Hmm, since monotone branches are always of the whole tree, I think we
> get this for free?
>
> Unless one of the features here is that as changes are committed to
> the team repo are automatically they automatically become visible in
> the personal repo, _unless_ you have branched that file locally?
>
> That sounds like a terrifying concept to me, guaranteeing that you can
> never reconstruct tree states later, but perhaps it is a feature?  I
> would certainly like to understand, even if I happen not to like the
> result :-).
>

You understand correctly:-) You have to use a label for the team branch (not 
LATEST) or you're in deep trouble in a day or two :-)

/Johan