Thus said Jan Nijtmans on Thu, 07 Nov 2013 12:41:01 +0100: > The merge of those two branches didn't have any conflicts, and > everything works fine.
I found another case where things weren't working entirely as expected: SSH urls. When cloning via: fossil clone ssh://user:password@remote//tmp/test.fossil clone.fossil It would prompt me to save the password, which is not correct. The SSH user does not need a password saved because the password is not used. I fixed that up and also slightly changed your clone --once (it now looks a lot more like the sync --once option): http://www.fossil-scm.org/index.html/info/ad34c07c45 So we might want to add SSH urls to your test matrix. The only other URL type is HTTPS which should mostly behave the same as HTTP URLs with the exception that an HTTPS URL could connect using a peer certificate that actually could be used for Fossil authentication if REMOTE_USER is enabled (or it could be used for simply authenticating to the HTTPS server, followed by Fossil user authentication). Thanks, Andy -- TAI64 timestamp: 40000000527c80e2 _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
