What do I call a working tree that stores its revisions in a shared repository?

[Talden]

On Tue, Apr 1, 2008 at 1:31 AM, Paul Moore <p.f.moore at gmail.com> wrote:
> On 30/03/2008, Talden <talden at gmail.com> wrote:
>  > >  PS Given that it's possible to copy standalone trees *far* faster than
>  > >  "bzr branch"-ing them, is there any reason not to create a branch via
>  > >  copying instead of branching?
>  >
>  > When you want to move them, branch them.  That way I assume you'd only
>  > be wearing the cost of the branching in the exceptional cases. Unless
>  > of course you expect to be copying and moving trees around all the
>  > time.
>
>  I think you missed my point. On my PC, with the Python trunk, bzr
>  branch to a standalone tree takes 8 minutes, whereas copy /s/h only
>  takes about 2 minutes. That's significant enough to make me want to
>  copy where possible.

Actually I think you missed mine - but that was my fault. The
paragraph you've quoted really was a poorly worded reference to this

>  > >  Oh, and while I'm on the subject, that's a significant problem with
>  > >  shared repositories in some situations, the fact that you *can't*
>  > >  treat them as independent objects (zip them up, move them around,
>  > >  email them, etc).

In that I assume the 'zipping up' or 'moving them around' is the rarer
event than your normal workflow and therefore you should:

- Use a shared repository in normal workflow
- Use branch to an area outside the shared repo to create standalone
branches when needed.

Of course that's all based on what's currently supported.  As I noted,
it would be nice to have support for converting branches to/from a
shared repo.

--
Talden