[RFC] New name for 'repositories' - 'baskets'

[Erik Bågfors]

2006/3/6, David Allouche <david at allouche.net>:
> On Mon, 2006-03-06 at 11:53 +1100, Robert Collins wrote:
> > On Sun, 2006-03-05 at 14:18 +0100, David Allouche wrote:
> >
> > > What I meant is that I wish bzr would not impose arbitrary restrictions
> > > on what the repository-in-a-standalone branch can do. That I wish it
> > > would be functionally equivalent to a shared repository.
> >
> > Its not arbitrary...
> >
> > We decided at UBZ that:
> >
> > $ bzr branch $SOMEWHERE dir
> > $ bzr branch $SOMEWHEREELSE dir/subdir
> > $ mv dir/subdir otherdir
> > $ rm -rf dir
> >
> > should -never- invalidate the content of otherdir.
> >
> > If a standalone branch acts as a shared repository, that use case will
> > fail.
>
> If I understand correctly, that would mean that
>         bzr branch $SOMEWHEREELSE dir/subdir
> would create a dir/subdir branch that uses the repository of dir/.
> Indeed that looks like a bad idea. Nested trees should not behave like
> repositories.
>
> What I was thinking was something along the lines of:
>
> $ bzr branch $SOMEWHERE dir
> $ bzr branch --no-repo dir otherdir
>
> To create an "otherdir" branch that uses "dir" for its repository. For
> example by storing the URL it was branched from in .bzr.

I don't understand. Why do you use "no-repo" to indicate that it
should use a repo at "dir"?

/Erik