sftp oddities

[Jeff Rose]

Hello again,
  I was thinking it could be helpful to bring up issues as we jump into
bazaar, but if this isn't the right forum let me know.  Both of my
roommates and I are grad students in CS with years of cvs/svn under our
belts, and we probably represent the type of people you hope to bring to
bazaar as time goes on.  Hopefully our perspectives can be
constructive...

1. Why does pushing and branching with sftp use an odd url that doesn't
correspond with what people already know about sftp?  Why not use a
colon after the hostname, and then if you have a slash it goes to the
root of the fs, like the normal utils?

sftp://foo.com:/home/myfriend/code/project

otherwise you have to do this, which seems pretty weird:

sftp://foo.com/../myfriend/code/project

  Pushing a fresh tree (at least with sftp) prints a warning that makes
you think it has failed:

--------------------------------------------
rosejn at jive:~/code/icalendar$ bzr push
sftp://research.inf.unisi.ch/code/icalendar
bzr: WARNING: Unable to update the working tree of:
sftp://research.inf.unisi.ch/code/icalendar
7 revision(s) pushed.
--------------------------------------------

Then checking the remote branch to see if it did indeed work, we find an
empty project directory.  Branching seems to work fine though, so I
guess it rebuilds the working tree when you pull it down?

-Jeff