Thus said Jan Nijtmans on Tue, 05 Nov 2013 11:14:07 +0100: > I now added the --once option to "fossil clone".
I hinted at this before, but now I understand what is going on so I can communicate it properly. Basically, there is a minor caveat when using clone --once due to the recently introduced clone behavior that causes the default admin user to be inherited from the URL user. After cloning with --once, any operations in the opened fossil won't know who the user is (including setting the default). $ 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 Obviously it works if I follow the instructions: $ env USER=tester fossil up ------------------------------------------------------------------------------- checkout: b38c9acbd0d69412f25d60b3c2da2096f092b53b 2013-11-08 05:18:55 UTC tags: trunk ... Does this need to be documented more than what is already displayed here (e.g. the warning from fossil up and fossil user)? Andy -- TAI64 timestamp: 40000000527c7c6d _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
