On Mon, Apr 11, 2011 at 11:13 AM, Thomas Goirand <tho...@goirand.fr> wrote: > It unfortunately does. "bzr launchpad-login" for example does, and if
I'll ask the bzr team to think about how to make this more discoverable, but this will help: bzr launchpad-login --no-check <username> All it's really doing is setting the launchpad_username in ~/.bazaar/bazaar.conf , the --no-check flag tells it to skip asking launchpad if this is a valid username. In my config file it looks like this: [DEFAULT] launchpad_username = statik > I'm not mistaking or dreaming, "bzr commit" as well. Using Git, it's not > the case. The issue isn't to cache data, the issue is that a commit > should *never* access any remote data, so that I could work in the train > without connectivity, for example, and still be able to do "bzr commit". > Only pull and push should do network accesses. Fully agreed, and I believe that bzr operates this way by default - certainly I rely on commit never touches the network, only the initial branch and then push and pull. It is possible to configure bzr (I think using a checkout bound to a remote branch - did you do bzr checkout instead of branch perhaps?) so that it works more like subversion, where a commit does go over the network and update the parent, but I never use that mode and believe that disconnected is the default, just like with git. Thanks for all the details you sent, it's very helpful. -- Elliot Murphy | https://launchpad.net/~statik/ _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
