Re: [fossil-users] Apparently a bug in ticketing

2017-05-23 Thread Andy Bradford
Thus said Doug Franklin on Mon, 22 May 2017 18:32:00 -0400: > 11. Oops. I don't have three tickets. I have two tickets. The first > ticket is fine. The original second ticket seems to be gone (it's not > in the "All tickets" list), and the current second ticket has all of > the values of

Re: [fossil-users] Apparently a bug in ticketing

2017-05-23 Thread Andy Bradford
Thus said Doug Franklin on Mon, 22 May 2017 18:32:00 -0400: > 11. Oops. I don't have three tickets. I have two tickets. The first > ticket is fine. The original second ticket seems to be gone (it's not > in the "All tickets" list), and the current second ticket has all of > the values of

Re: [fossil-users] [SPAM] Re: [fossil-dev] Bug - Fossil source "printf.c"

2017-05-23 Thread Richard Hipp
On 5/23/17, David Simmons wrote: > > The details of the second issue are/were explained in the > fixed-source-code's revision comments that was in the original e-mail > posting. > Where in the Fossil source code is a %s printf conversion being pass a string which is not

Re: [fossil-users] [SPAM] Re: [fossil-dev] Bug - Fossil source "printf.c"

2017-05-23 Thread David Simmons
As the e-mail said, it was "clang" that was used as the compiler. There are two distinct considerations. The first was in etBUFFSIZE signed/unsigned promotion, which arose from the looseness of c-typing rules and signed/unsigned promotion versus c++. It otherwise is not critical, while