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

[Paul Moore]

On 31/03/2008, Talden <talden at gmail.com> wrote:
> 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.

Ah, sorry. I see. My point was different - I don't like shared
repositories because of the organisational limitations they impose, so
I prefer to use standalone branches. However, they are too slow to
use, so to get a reasonable level of speed back, I'm considering using
an OS copy rather than a bzr branch.

I agree that if I was comfortable using shared repositories, my point
about copies would be more or less irrelevant.

On the other hand, maybe shared repositories would add a much needed
level of organisation to my currently disorganised coding habits :-)
But let's not go there right now.

Sorry for the confusion.
Paul.