This one time, at band camp, John A Meinel wrote:
>It does include the information, though not necessarily in the form that
>you were expecting:
>
>publish to branch:
>sftp://<email address hidden>/~/repo/zookeepr/mainline/
>
>That means that you are bound.
Ah. I thought that meant "when I type bzr push it'll publish there".
>We are suffering from a terminology problem. Where a 'bound branch' is
>being called a 'checkout'. And in general we are trying to get away from
>the 'bound/unbound/bind/unbind' terminology, because it doesn't work
>well with 'checkout' concepts that people are used to.
>
>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. :)
This one time, at band camp, John A Meinel wrote: /~/repo/ zookeepr/ mainline/
>It does include the information, though not necessarily in the form that
>you were expecting:
>
>publish to branch:
>sftp://<email address hidden>
>
>That means that you are bound.
Ah. I thought that meant "when I type bzr push it'll publish there".
>We are suffering from a terminology problem. Where a 'bound branch' is unbound/ bind/unbind' terminology, because it doesn't work
>being called a 'checkout'. And in general we are trying to get away from
>the 'bound/
>well with 'checkout' concepts that people are used to.
>
>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. :)