Unexpected behavor in branch and push...

[John A Meinel]

James Blackwell wrote:
> 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?
> 

The reason bzr branch doesn't support sftp is because it wants to create
a working tree. And we only support local working trees.
We could certainly update that.

I think we really only need one command to create branches. Especially
if we support targets, then you can do:

bzr branch sftp://myhost/branch1 sftp://myhost/branch2

And we can make bzr smart enough to use a remote copy rather than
downloading and uploading everything.
I think it is actually not very hard to do with the current Transport
stuff. Just use "copy_to", and have it recognize that the target is also
SftpTransport, and connected to the same host. (which if we bring in a
ssh mapping, so that we only connect to one server once, it gets even
better).

> 
>> The same actually happens locally.  If I do "bzr push ../newbranch"
>> that works.  But if I do "bzr pull ../oldbranch" I get a
>> bzrlib.errors.NotBranchError back.
>>
>> I think that "bzr push" should work like "bzr pull" and "bzr branch"
>> should work with remote storage.
> 
> I hear you. I have an alternative opinion myself. 
> 

I'm okay with push creating branches, but I would prefer if it didn't
and bzr branch was used for that sort of thing.

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/20051115/4cbe43b6/attachment.pgp