Thus said Jan Nijtmans on Sat, 02 Nov 2013 12:11:51 +0100: > I just made a little modification preventing the prompt if the saved > password is already equal to the to-be-saved password. I will do some > more testing the coming days, but I think the "pending-review" branch > (another name would be better....) works fine as I expect.
I have made further modifications for some other cases and I think it's nearing completion (if not already there). In addition to the clone/sync/push/pull operations that you mentioned for test cases, we should also add update/commit/remote-url operations. While it isn't possible to use --once with update/commit/remote-url, there is the possiblity that a new password will be required for each of these and it will prompt to ``save the password'' during these times. For example, a users password might have been updated since the last time he did an update and the first time he tries to commit, it might prompt for the new password, and then ask to save it. I have tried to test as many of these scenarios as possible, but as always, more eyes are better. Thanks for your help. Andy -- TAI64 timestamp: 4000000052787525 _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
