This one time, at band camp, Robert Collins wrote:
>On Wed, 2006-09-06 at 02:50 +0000, Jamie Wilkinson wrote:
>>
>> >If you can think of a way to say it, rather than 'publish to', that
>> >works well with 'checkout' and possibly with 'bound'. Feel more than
>> >free to suggest it.
>>
>> Yeah, I didn't realise it was also affected by checkouts, which I
>> don't use.
>> I don't have any ideas on how better to say it. :)
>
>A 'bound branch' *IS* a checkout, which is why we want to eliminate the
>term 'bound branch' - its seriously confusing.
This one time, at band camp, Robert Collins wrote:
>On Wed, 2006-09-06 at 02:50 +0000, Jamie Wilkinson wrote:
>>
>> >If you can think of a way to say it, rather than 'publish to', that
>> >works well with 'checkout' and possibly with 'bound'. Feel more than
>> >free to suggest it.
>>
>> Yeah, I didn't realise it was also affected by checkouts, which I
>> don't use.
>> I don't have any ideas on how better to say it. :)
>
>A 'bound branch' *IS* a checkout, which is why we want to eliminate the
>term 'bound branch' - its seriously confusing.
Really? I didn't check it out, I ran:
bzr get sftp:// dawn/~/ src/snuh/ bar dawn/~/ src/snuh/ bar
cd bar
bzr bind sftp://
which to me says "I made a new branch, and then bound it," not "i checked
out an existing branch".
At any time I can bzr unbind this and it's now a separate branch, and then I
can push or merge back to the parent before binding again.
So, conceptually, it's not a checkout, and I'd never have thought that it
was until you mentioned it in this bug.
If you want to eliminate the term, then you need to eliminate the commands
'bind' and 'unbind'. What you replace/rename them with, I don't know.