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
Thus said Stephan Beal on Mon, 06 Oct 2014 17:23:22 +0200:
http://www.fossil-scm.org/index.html/info/165cc5c093e6ee36a78de5e01f7049235dbc1b1c?ln=1856-1867
Could i convince you to give that look?
Yes, I'll look at it again later. I looked at it briefly before just
long enough to remind
Stephan, Andy,
Thanks for the quick action re my issue. I'll test it as soon as I have a
little more time (end of this week?).
Best,
Jacek
2014-10-06 16:23 GMT+01:00 Stephan Beal sgb...@googlemail.com:
On Mon, Oct 6, 2014 at 6:24 AM, Andy Bradford amb-fos...@bradfords.org
wrote:
After
Thus said Stephan Beal on Sat, 04 Oct 2014 21:36:33 +0200:
Before this change autosync_loop() did not consider login-prompt
failure to be an error. This seems to be an unusual corner case, and
i'm not sure which behaviour (old or new) is optimal for this case.
Thanks for tracking this
Thus said Stephan Beal on Sat, 04 Oct 2014 21:36:33 +0200:
If you suspect this change may have unwanted side effects on
other (non-clone) client_sync()-using routines, please voice your
suspicions!
After looking at it, I don't think this introduces any unwanted side
It is by design, and is a long-standing behaviour, but whether it's truly
required to be so (in terms of the internals), i don't know off-hand. Will
look at whether it's easy to get around that when i get back in town this
evening.
- stephan
Sent from a mobile device, possibly from bed.
On Sat, Oct 4, 2014 at 9:55 AM, Stephan Beal sgb...@googlemail.com wrote:
It is by design, and is a long-standing behaviour, but whether it's truly
required to be so (in terms of the internals), i don't know off-hand. Will
look at whether it's easy to get around that when i get back in town
On Sat, Oct 4, 2014 at 9:22 PM, Stephan Beal sgb...@googlemail.com wrote:
Management summary: fixed now:
http://www.fossil-scm.org/index.html/info/334d7744021dba7be0a34d88aacb32a9a4860291
The cause was that the password prompt did not consider the 3rd failure to
be an error,
Correction:
Hi all,
I've noticed an unexecpected behaviour in fossil when doing a clone. The
issue appears when you try clone with a wrong user name and as the result
an empty repo is created. I'd rather expect an error on the console and
nothing else.
The thing is fully reproducible with the latest windows
9 matches
Mail list logo
