bzr pull vs. bzr update

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Juanma Barranquero wrote:
> On Thu, Dec 17, 2009 at 06:08, John Arbash Meinel
> <john at arbash-meinel.com> wrote:
>> Though again, our standard documentation would say "use bzr co $MASTER;
>> bzr up". (And 'bzr pull' doesn't just work there because 'bzr co'
>> doesn't set the parent pointer because it expects you will be using
>> 'update'.)
> 
> I think part of the problem, then, is that this kind of information
> seem to be documented nowhere but the source.
> 
>> *Personally* I would
>> rather make bound branches more first class than trying to make
>> heavyweight checkouts act like lightweight checkouts.
> 
> This is again confusing; not the difference between heavyweight and
> lightweight checkouts (that's clear), but betwen "bound branches" and
> "checkouts". You mentioned above that checkout does not set the parent
> pointer. But the doc for bind says:
> 
>   Purpose: Convert the current branch into a checkout of the supplied branch.
> 
> so a newbie (like myself) would expect that bzr brach + bzr bind ==
> bzr checkout.
> 
> (BTW, this is not about Emacs anymore; perhaps I should file a
> bug/request to improve the docs.)
> 
>     Juanma
> 

branch + bind == checkout is correct. It just happens that the original
"branch" command sets the parent pointer, while "bzr checkout" would not.

As soon as you did a pull into the checkout, the parent pointer would
get set to the target of the pull. It just isn't defaulted (as we don't
specifically expect you to 'bzr pull' to update from the master, as we
would expect you to use 'bzr up' for that.)

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAksqXf4ACgkQJdeBCYSNAAOpEwCg2jBpG3eXWreBC55Omwd+qbPo
9tYAoJ0A1N6GYaIC/ugVCafDtzFFjrPW
=vyNF
-----END PGP SIGNATURE-----