2008/7/11 James Westby <<a href="mailto:jw%2Bdebian@jameswestby.net">jw+debian@jameswestby.net</a>>: <div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div class="Ih2E3d">On Wed, 2008-07-09 at 22:24 -0600, Scott Scriven wrote: > This is a fix for bug 247150.  It makes 'bzr init-repo' work in a > fresh directory.  Otherwise, this happens: > >   % mkdir foo ; cd foo >   % bzr.dev init-repo >   bzr: ERROR: command 'init-repository' requires argument LOCATION </div>I asked about this behaviour not too long ago, and John said it was intentional, as a kind of safety catch. Accidentally setting up a shared repository can lead to your data not being stored where you thought it was, which could be disastorous. However, I don't know if that's a big enough concern to force the inconsistency with "init" here.</blockquote></div> I think this will be good (to be consistent with init). And its not much of a disaster  if  your  new branches are configured to use a shared repository, since we now have the `reconfigure` command which will make recovery very easy. (I see the reconfigure help needs some love, as it took me a while to figure out how to use it ) What may help to reduce unexpected behavior, is if these commands can be made more verbose: print `bzr info` after the init/init-repo.  Then you would know what happened. I see that these commands never print anything, even if you run them with -v /--verbose. But thats for another patch to fix. Let me know if anybody would have and issue if I make these commands print something by default. regards marius