push over sftp

[Erik Bågfors]

2005/11/3, Joachim Nilsson <joachim.nilsson at vmlinux.org>:
> On Wed, 2005-11-02 at 18:44 -0800, Robey Pointer wrote:
> > On 2 Nov 2005, at 15:57, Joachim Nilsson wrote:
> > > I find absolute paths annoying, so I may look
> > > into that if I get the time and noone else beats me to it. :)
> > The last time I looked, the sftp url IETF drafts allowed only
> > absolute paths, but if you all can come up with a reasonable
> > convention for relative paths, I'm all for it.  Having only absolute
> > paths bugs me too. :)
>
> I was thinking along the lines of scp/rsync paths.  The ':' (colon)
> separator is very useful to separate a local host from a remote one. I
> have seldom had the need to use ports other than the default, for that a
> --port PORT switch seem more appropriate to me, even though rsync
> supports the :PORT syntax.  I'll have a look at it later.

I agree. I use "scp file host:public_html/path" quite alot and it
makes sense to public a repo with "bzr push host:public_html/repo". 
This is also host darcs does it.  It uses url for http but just
"host:path" for ssh paths.

To be fair that's all the darcs can handle really, http and ssh. But
bzr will be able to handle alot more types of systems, smart remote
servers, ftp servers, etc, so maybe it doesn't make sense to make sftp
a special case?

It may be more "correct" to use "sftp://" but it's also more
complicated (and lot's longer due to the absolut patch requirement) to
write on a command line.

Regards,
Erik