* Marius Kruger wrote:
> Ok, so it can still be disastrous, if you accidentally make a repository within a repository,
> where there is existing branches in the new repository's jurisdiction.
>
> Since this is possible at the moment and it can big problems especially if it goes
> undetected. I think we should at least give a warning if you create a
> repository within a repository, or even better detect if we are
> screwing up branches (but that could be very difficult/slow).
* Robert Collins wrote:
> I think that having an implicit '.' as the location should wait for the
> potential confusion to be detected by init-repo; yes there are potential
> performance implications in doing this.
Launchpad doesn't yet have a "later" bug status or bug dependencies, so I'll just leave this open for now.
This change is waiting on some other fixes. A few messages from the mailing list explain further:
* Robert Collins wrote:
> init-repo can affect existing branches:
>
> bzr init-repo foo
> mkdir foo/bar
> bzr branch SOMETHING foo/bar/baz
> bzr init-repo foo/bar
> bzr check foo/bar/baz
* Marius Kruger wrote:
> Ok, so it can still be disastrous, if you accidentally make a repository within a repository,
> where there is existing branches in the new repository's jurisdiction.
>
> Since this is possible at the moment and it can big problems especially if it goes
> undetected. I think we should at least give a warning if you create a
> repository within a repository, or even better detect if we are
> screwing up branches (but that could be very difficult/slow).
* Robert Collins wrote:
> I think that having an implicit '.' as the location should wait for the
> potential confusion to be detected by init-repo; yes there are potential
> performance implications in doing this.
Launchpad doesn't yet have a "later" bug status or bug dependencies, so I'll just leave this open for now.