Thank very much for your feedback!
Warren Young:
> Which is it?
With the random appearance of the delay, and the long duration of 60
seconds, I eventually gave up on "bisecting".
But with a more systematic approach, I've now got:
Last good: [06507038]
First bad: [947081aa]
> If the problem
> ... writing to a FILE* pointing to NULL may have exactly the same
> effect as writing to a FILE* pointing to "/dev/null"?
Well, unless there's a directory named "dev" in the root of the
current drive, which would result in creation (due to the passed "wb"
mode) of a file named "null", on
Richard Hipp:
> Please test the latest trunk version and let me know if you are still
> seeing issues.
Thank you very much for the fix!
I see no more delays with "fossil ui" on Windows.
Just a thought: would it make sense to have --nodelay as a global
option recognized by all commands, and
Warren Young:
> Quantify “a lot.”
I have some rarely committed-to but frequently web-accessed
repositories (with login), and I see daily backups of the modified
repository database, even though I'm sure I haven't committed
anything. It's like "hey, what's going on there with my babies?"
It's not at all that I think I'm the expert you've summoned in your
last post on this thread. As you've been running your own high-traffic
"althttpd" server for many years, maybe you should explain the
Internet to us.
I was doing some (limited) research about RFCs, recommendations from
the Apache
101 - 105 of 105 matches
Mail list logo
