[prev in list] [next in list] [prev in thread] [next in thread] 

List:       bitkeeper-users
Subject:    RE: [Bitkeeper-users] bk grandparent
From:       "Brown, Len" <len.brown () intel ! com>
Date:       2003-06-11 20:51:13
[Download RAW message or body]

> From: Larry McVoy [mailto:lm@bitmover.com] 
> The bigger problem is that "parent" is a misnomer.

I guess the best practice is be to give a tree a descriptive name that tells
you its semantic context -- eg. In this example "linux-acpi-2.4" and
"linux-acpi-2.5" -- because the access pattern may be much more complicated
than simple parent/child.

But when the name is too vague it would be nice to be able to observe the
default parent as a way of identifying the origin of the tree -- even if it
isn't used in practice for push/pull.  If bk parent or bk status could
understand a remote http tree, that would do it.

Cheers,
-Len

_______________________________________________
Bitkeeper-users mailing list
Bitkeeper-users@bitmover.com
http://bitmover.com/mailman/listinfo/bitkeeper-users
To unsubscribe from this list, go to the above URL, follow instruction at the bottom of the web page.
[prev in list] [next in list] [prev in thread] [next in thread]