Bzr checkout vs. bzr get

I wonder what is the difference between

bzr checkout ./MyProject MyProject.dev
# later followed by a
cd MyProject.dev
bzr pull ../MyProject

and

bzr get ./MyProject MyProject.dev
# later followed by
cd MyProject.dev
bzr pull

As far as I can tell, the only difference is this:

  • bzr get sets the location of the pull.
  • bzr checkout does not set the tension location, so it must be specified the first time you pull.

Are there any other differences?

+3
source share
4 answers

bzr getcreates a branch, while bzr checkoutcreates a check. When checking, any changes you make to MyProject.devwill also be tied to MyProject.

For details, see the tutorial for design .

+6
source

bzr checkout bzr pull, bzr update.

bzr get bzr branch, git clone.

+7

Bazaar, : , , .

git DVCS? . bzr.

svn , ? "... , , , ? , !" . bzr checkout.

- Bazaar, , git .

+3

Basically, you have the option not to bind to the branch from which you got the code: if you want the offline copy to use bzr get, if you want to bind automatically to the source branch: use bzr checkout.

If you change your mind later and want it to look more like SVN, you can do bzr bindit and any commits you made will be automatically transferred to the parent branch.

+2
source

Source: https://habr.com/ru/post/1726895/


All Articles