Thus said Jan Nijtmans on Tue, 05 Nov 2013 11:14:07 +0100: > I now added the --once option to "fossil clone". I can only think of > one use-case: when cloning a repository where autosync is going to be > off, which is going to be synced automatically using a script > containing "fossil sync --once http://user:passwd@host";. In that case > I can imagine we don't want the url/passwd to be saved.
More than just the URL/password are not saved: $ fossil clone --once http://tester:testing@localhost:8081/ clone.fossil Round-trips: 2 Artifacts sent: 0 received: 7 Clone finished with 533 bytes sent, 1730 bytes received Rebuilding repository meta-data... 100.0% complete... project-id: 7aa96a33ca6788aab4a9301272c56e1148fac3a9 admin-user: tester (password is "6acd8c") $ fossil open ../clone.fossil file project-name: <unnamed> repository: /tmp/clone/../clone.fossil local-root: /tmp/clone/ ... $ fossil user default Cannot figure out who you are! Consider using the --user command line option, setting your USER environment variable, or setting a default user with "fossil user default USER". cannot determine user $ fossil up Cannot figure out who you are! Consider using the --user command line option, setting your USER environment variable, or setting a default user with "fossil user default USER". cannot determine user But, as you point out, if the use case is to repeatedly update the clone with fossil sync --once commands, then I suppose this is expected. If I follow it up with: fossil sync http://tester@localhost:8081/ It does work as expected too (prompts for password, saves, etc...) Thanks for the help. Looks like it might be ready? For the purposes of testing, I've been testing the negative response to the question as well (we wouldn't want to save the password if the user answered No). Andy -- TAI64 timestamp: 400000005279cdee _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
