accept USER@HOST:PATH as a shortcut for ssh
Bug #337456 reported by
Martin Pool
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Confirmed
|
Medium
|
Unassigned | ||
| Breezy |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
split out from bug 121195: rsync, scp and others accept USER@HOST:PATH as a shortcut for running ssh. It's certainly easier to type, and this shortcut is fairly commonly accepted. It's also unlikely to be confused with anything else.
Rather than specially privileging rsync, perhaps we should have a configuration saying what the default transport is for connecting to a remote machine, either in general or for particular hosts. It could default to ssh.
| Changed in bzr: | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
Revision history for this message
| Samuel Bronson (naesten) wrote | #1 |
| tags: | added: sftp ssh ui |
| tags: | added: check-for-breezy |
| tags: | removed: check-for-breezy |
| Changed in brz: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
To post a comment you must log in.
Others include sftp, git and darcs.
sftp wants a "Subsystem sftp <path>" in the remote sshd configuration, but it can also just execute the "sftp-server" program remotely.
Git wants "git-upload-pack" on the remote for clone/fetch/etc. and "git-receive-pack" on the remote for push. Darcs needs "darcs" remotely, at least for push (and doesn't seem to provide a way to handle the case where it isn't in PATH!). For pull, I suspect darcs may use the scp protocol but am having trouble finding it in the manual.
Mercurial doesn't seem to support the short form, but does require "hg" on the remote.
So it seems that "bzr+ssh://" would be a reasonable default default, as most programs that support such a short form seem to expect themselves (or at least significant portions of themselves) to be installed remotely.