Unexpected behavor in branch and push...

[Erik Bågfors]

2005/11/16, James Blackwell <jblack at merconline.com>:
> On Tue, Nov 15, 2005 at 11:05:18AM +0100, Erik Bågfors wrote:
> > I'm suprised to find that "bzr branch branchname sftp://host/path"
> > doesn't work. Instead I can, in "branchname" run "bzr push
> > sftp://host/path".
>
> bzr branch not handling sftp sounds like a bug to me.
>
> > I was expecting push to only be able to push to an already existing branch.
>
> What sort of problems do you expect with push being able to create a new
> branch?

Simple, typing things wrong and not understanding it.

For example,
Developer1: I have a new feature in my branch, do you want it,
Developer2: Yes, push it to sftp://foo/blaha1
Developer1: bzr push sftp://foo/blah1
Developer1: I don't need this anymore, rm -rf

And developer2 didn't get it, well, he has it but in the wrong place
and maybe there were conflicts that Developer1 should have fixed etc.

If it at least would give you feedback saying that it creates a new
branch, I'm ok. but just quitely doing something unexpected is not
good.

If push can create a new branch, I think pull should also.

/Erik