push + bind in a single operation ?

Robert Collins robertc at robertcollins.net
Wed Sep 20 01:17:58 BST 2006


On Tue, 2006-09-19 at 10:34 +0200, Erik Bågfors wrote:
> On 9/19/06, Matthieu Moy <Matthieu.Moy at imag.fr> wrote:
> > John Arbash Meinel <john at arbash-meinel.com> writes:
> >
> > > Perhaps:
> > >
> > > bzr push --make-checkout
> > >
> > > Would be reasonable?
> >
> > With the ambiguity that one doesn't know from the name of the command
> > if the local branch or the newly created remote one will be the
> > checkout.
> 
> Well, since pull + bind = checkout, it's only logical that push + bind
> = checkin :)
> 
> 
> > But "bzr push --make-local-checkout-of-remote" is probably
> > overexagerated ;-) and I can't think of any better.
> >
> > BTW, this also raises the old question about whether "branch" or
> > "push" should be used to create a new remote branche.
> 
> I'm a big fan of letting pull and push be each others opposites.  so,
> I vote branch.

branch is used to create a new line of development, which this isn't
doing: its creating a mirror of the current line of development, *and*
making the current branch a checkout of the remote.

I agree a one-shot command is needed. I also agree that push --checkout
or push --create-checkout is ambiguous at best about which is a checkout
of which.

At the risk of adding new terms, perhaps 'bzr push
--create-shared-branch'? Or maybe 'bzr push --convert-to-checkout' -
which implies the current branch (cant convert something that does not
exist)

-Rob

-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060920/b43bad2e/attachment.pgp 


More information about the bazaar mailing list