bzr init allows a repo to be set up within another repo
Bug #299346 reported by
Andy Grover
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Confirmed
|
Wishlist
|
Unassigned | ||
Bug Description
Running bzr init in a subdirectory of an existing repo creates another repo, and commits are added to the inner repo. This is bad.
I just spent a chunk of time educating some of my fellow developers (new to bzr) to not do this. The only cases where I can see a repo inside another repo being useful are fringe cases. I'd like to see bzr init within an existing repo fail, unless perhaps a --force option is given.
| Changed in bzr: | |
| status: | New → Confirmed |
| importance: | Undecided → Wishlist |
| tags: | added: ui |
Revision history for this message
| Robert Collins (lifeless) wrote Re: [Bug 299346] [NEW] bzr init allows a repo to be set up within another repo | #1 |
| tags: | added: check-for-breezy |
To post a comment you must log in.
On Tue, 2008-11-18 at 06:39 +0000, Andy Grover wrote:
> Public bug reported:
>
> Running bzr init in a subdirectory of an existing repo creates another
> repo, and commits are added to the inner repo. This is bad.
>
> I just spent a chunk of time educating some of my fellow developers (new
> to bzr) to not do this. The only cases where I can see a repo inside
> another repo being useful are fringe cases. I'd like to see bzr init
> within an existing repo fail, unless perhaps a --force option is given.
FWIW, I do this, and so do others quite regularly - consider that if you
have ~ (or any other containing directory) under version control, you
have a repository there.
-Rob