Thus said Martin Gagnon on Wed, 24 Jul 2013 20:44:05 -0400: > But it seems that now, if I have a user in the URL and a -l > <user> argument, the user from the URL is used for the fossil > authentifcation.
Thanks for pointing it out: http://www.fossil-scm.org/index.html/info/90ee2ee528 Let me know if you notice anything else. There is one thing which needs some work if possible. If you are not using SSH keys, the prompt for your SSH password ends up on top of the Round-trips status line: $ fossil clone -l guest ssh://amb@remote//tmp/new.fossil clone.fossil password for guest: remember password (Y/n)? y Round-trips: 1 Artifacts sent: 0 received: 0 ssh -e none -T amb@remote fossil http /tmp/new.fossil amb@remote's password: amb@remote's password: cts sent: 0 received: 1 Round-trips: 2 Artifacts sent: 0 received: 3 Clone finished with 546 bytes sent, 1157 bytes received Rebuilding repository meta-data... 100.0% complete... project-id: c0963fbe84473812993cee1f46d6ce6eb890c05f admin-user: amb (password is "63231d") This is because the SSH prompt is writing on top of the Round-trips line which doesn't include a newline. Of course this isn't present if there is no authentication required (SSH keys in use with ssh-agent or no passphrase on key, or in the case of an anonymous SSH fossil account), and so it looks nicer. I'll take a look, but I'm not sure there is anything that can be done about the case where it prompts for a password, but it can be a bit confusing to see the password prompt mixed in with the Rount-trips output. Thanks, Andy -- TAI64 timestamp: 4000000051f086da _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
