Simplified Tutorial
Jari Aalto+usenet
jari.aalto at cante.net
Thu Jun 29 15:19:42 BST 2006
* Sat 2006-05-06 John Arbash Meinel <john AT arbash-meinel.com>
* Message-Id: 445CDC18.2080105 AT arbash-meinel.com
>> Nope. /path/to/repo is just a shared repository, not a branch. A
>> repository cannot contain any files (only revisions and branches). The
>> branches in the repository does not have working trees, so a checkout
>> has to happen to add files to it. Same as in svn I think... at least
>> that's how I've always worked with svn.
>>
>> /Erik
>
> bzr init-repo --trees /path/to/repo
>
> Then by default, new branches created there will have working trees. I
> use it in my working directory, so that I can have 10 development
> branches of bzr, which all share the same history storage.
Hm.
The "shared repository"
init-repo --trees (shared history for all?)
+-----------------------------------------
| init - creates an empty branch
| - creates checkout (empty working tree)
|
| branch - creates a new branch
| - does not checkout
+------------------------------------------
So the command hierarchy is something like:
init-repo --trees
init | branch
checkout - light "branch"
checkout --lightweight - even lighter "branch"
but then I got lost after seing John's commands. Page [1] reads "The
checkout will create a working tree.", but I don't really grasp what
that means from user's perspective in relation to a "branch" command:
bzr branch (syn. "get")
bzr checkout
Jari
[1]
http://bazaar-vcs.org/SharedRepositoryTutorial
> Also, even without the above, you can do:
>
> bzr init-repo /path/to/repo
> cd /path/to/repo
> bzr init newbranch
> cd newbranch
> # Bzr 'init' always creates a checkout
>
> Or
> cd /path/to/repo
> bzr get sftp://host/other/branch tohere
> cd tohere
> bzr checkout
> # The above will create a checkout into the local directory.
> # Basically just creates a working tree for the branch you
> # are currently sitting in.
More information about the bazaar
mailing list