Understanding pull

Erik Bågfors zindar at gmail.com
Fri Mar 23 10:50:21 GMT 2007

On 3/23/07, Marius Kruger <amanic at gmail.com> wrote:
> it will only pull the revisions you don't have
> and it can be done even after you changed some of your local files.
> it will merge the new stuff with your stuff and let you know if there
> were conflicts

As long as you haven't committed the changes.

>  the only ways in which your branch isn't a clone of the remote branch is
> 1) the revision order might be different

No, not any more. It used to be that way in bzr, but not anymore.
You're branches revision will be in the same order as the branch you
pull from.

> 2) your local changes will still only be in your local branch

Only uncommitted changes.

The end result by running
cd branch; bzr pull

rm -rf branch; bzr branch path/to/branch

is the same, if you don't count uncommitted changes in the working tree.


>  On 3/23/07, Ian Clatworthy <ian.clatworthy at internode.on.net> wrote:
> > Hi,
> >
> > Just trying to get my head around *exactly* what pull does. In
> > particular, the FAQ states "often when you pull, your local branch
> > becomes a clone of the other one.".
> >
> > Why does it say "often when you pull"? When will it not be a clone?
> >
> > To ask the question another way, how is pull different from deleting the
> > directory and running branch again (other than speed and bandwidth)?
> >
> > Ian C.
> >
> >
> --
> I code therefore I am.

google talk/jabber. zindar at gmail.com
SIP-phones: sip:erik_bagfors at gizmoproject.com
sip:17476714687 at proxy01.sipphone.com

More information about the bazaar mailing list