creating checkouts, bound branches and standalone branches from an existing branch

[John A Meinel]

Erik Bågfors wrote:
> 2006/2/11, Robert Collins <robertc at robertcollins.net>:
>> So we have a UI problem here..
>>
>> I can get some code in front of me to hack and commit on in three way:
>>  * Create a checkout
>>  * Create a bound branch
>>  * create a standalone branch
>>
>> The first one is under the hood a 'create a branch reference to URL' +
>> working tree operation. And I think at the UI clearly has to be 'bzr
>> checkout URL [PATH]'.
>>
>> The third one is (under the hood) a 'bzrdir(URL).sprout(PATH)'
>> operation, and is (again clearly) 'bzr branch URL PATH'
>>
>> But what about the bound branch case? Should that be 'get' ? or 'bzr
>> branch --bind' ?
> 
> Apart from the UI question, but should you be able to create a
> checkout or a bound branch from/to a stand alone branch.  I assume
> this will make the standalone branch's working tree out of sync from
> what's in .bzr, when someone checks in from the checkout/bound branch?
> 
> /Erik

You can create both a bound branch and a checkout to another branch.
Yes, this means the working directory can be out of date. But that is
why we want to add a 'last_revision' marker for the working tree, so
that it at least knows that it is out of date.

John
=:->


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 249 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060212/9dbec178/attachment.pgp