[MERGE] make init-repo use '.' as default location
Marius Kruger
amanic at gmail.com
Sat Jul 12 07:50:31 BST 2008
2008/7/11 James Westby <jw+debian at jameswestby.net<jw%2Bdebian at jameswestby.net>
>:
> 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
>
> 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.
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/bazaar/attachments/20080712/41e788b0/attachment.htm
More information about the bazaar
mailing list