The latest version of Fossil (in the self-hosting Fossil repository - not
the precompiled binaries which are a little too old) supports a new method
of pushing, pulling, cloning, and syncing using SSH. Examples:
fossil clone ssh://usern...@hostname.com/local/path/repo.fossilex1.fossil
On Wed, Aug 25, 2010 at 1:25 PM, Richard Hipp d...@sqlite.org wrote:
The latest version of Fossil (in the self-hosting Fossil repository - not
the precompiled binaries which are a little too old) supports a new method
of pushing, pulling, cloning, and syncing using SSH. Examples:
fossil
On 25/08/2010, at 3:46 PM, Brian Smith wrote:
On Wed, Aug 25, 2010 at 1:25 PM, Richard Hipp d...@sqlite.org wrote:
The latest version of Fossil (in the self-hosting Fossil repository - not
the precompiled binaries which are a little too old) supports a new method
of pushing, pulling,
On Wed, Aug 25, 2010 at 3:46 PM, Brian Smith br...@linuxfood.net wrote:
I'd vote for changing this notation to a more standard scp style reference.
I.e.: usern...@hostname.com:local/path or
usern...@hostname.com:/full/path.
I've got no strong opinions as to whether or not ssh:// is at the
On Wednesday 25 August 2010 23:25:03 Richard Hipp wrote:
The latest version of Fossil (in the self-hosting Fossil repository - not
the precompiled binaries which are a little too old) supports a new method
of pushing, pulling, cloning, and syncing using SSH. Examples:
fossil clone
I've got a fossil repo running on a shared virtual server. The hosting
company has locked sshd so the 'PATH' is only /bin and /usr/bin, which are not
writable for my user.
So when the ssh: tries to connect, it tries to launch 'fossil', which will not
work. I need to be able to say something
6 matches
Mail list logo
