Thus said Martin Gagnon on Wed, 10 Jul 2013 17:50:40 -0400: > Work fine now.. sorry for the noise..
Speaking of noise, time to add a little more (because my original email wasn't quite long enough). The new options that I've added are not yet fully documented in the usage/help (not having settled on how to access the changes in client). At the moment, you can specify which type of HTTP access to use (test-http vs http): fossil clone -h http ssh://amb@remote//tmp/test.fossil test.fossil Or if you prefer the old method (this option may be redundant): fossil clone -h test-http ssh://amb@remote//tmp/test.fossil test.fossil Path to fossil can be made explicit: fossil clone -f /opt/bin/fossil -h http ssh://amb@remote//tmp/test.fossil test.fossil Of course, if force command SSH keys are in use, it doesn't really matter what is specified because that will be controlled by the remote SSH account, in which case you might want to explicitly set the ssh command (in the even that the SSH key is different from your default SSH key): fossil clone -s 'ssh -e none -T -i /home/amb/.ssh/fossil' ssh://amb@remote//tmp/test.fossil test.fossil I wasn't certain if this was the right location to do this; can a repository specific SSH command be configured prior to cloning the repository? All of these options are also exposed in sync/push/pull (in the event that it needs to be changed). Andy -- TAI64 timestamp: 4000000051ddf842 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
