On Mon, Oct 6, 2014 at 6:24 AM, Andy Bradford <amb-fos...@bradfords.org> wrote:
> After looking at it, I don't think this introduces any unwanted side > effects. :-D > autosync-tries dictates how many times ``autosync'' should > ...autosync-tries would be honored and one would have to enter the password > for a maximum of 2 * autosync-tries. > That's what it looked like to me. Potentially annoying but harmless (and abortable with a Ctrl-C). > Maybe if we could distinguish between password failure and other > .... > Seems to me to be rare corner case which isn't necessary. Maybe in certain setups/uses, but i can't say i'd ever conceived of this "problem" until Jacek (the OP) posted it. > For the archives, here is what happens when I have autosync-tries set to > 2 and a password failure: > ... > Autosync failed. > continue in spite of sync failure (y/N)? n > $ > > Seems to behave as I would expect. Any other opinions? > Agreed. No "less surprising" result for that case comes to mind. But now that you mention autosync retry count... i'm not 100% sure i put that ++nErrs in the right place: http://www.fossil-scm.org/index.html/info/165cc5c093e6ee36a78de5e01f7049235dbc1b1c?ln=1856-1867 Could i convince you to give that look? -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
