On 7/27/2018 3:48 AM, Richard Hipp wrote:
On 7/26/18, Warren Young wrote:
Normally Fossil trunk is pretty stable at all times, but at the moment,
there are big changes afoot, so unless you plan to test and/or use those new
features, I think it’s best to stick to the current release.
There are
On 7/26/2018 7:46 PM, Warren Young wrote:
On Jul 26, 2018, at 7:28 PM, Ryan Noll (Mailing List)
wrote:
I upgraded via source to 2.6 (fd3198322a 2018-07-25 13:20:15 UTC)
Unless you need one of the changes between the 2.6 release made in early May
and the current trunk, I’d recommend staying o
On 7/26/18, Warren Young wrote:
>
> Normally Fossil trunk is pretty stable at all times, but at the moment,
> there are big changes afoot, so unless you plan to test and/or use those new
> features, I think it’s best to stick to the current release.
There are indeed big changes afoot. And yet, F
On Jul 26, 2018, at 7:28 PM, Ryan Noll (Mailing List)
wrote:
>
> I upgraded via source to 2.6 (fd3198322a 2018-07-25 13:20:15 UTC)
Unless you need one of the changes between the 2.6 release made in early May
and the current trunk, I’d recommend staying on release versions until the
current tr
On 7/26/18, Ryan Noll (Mailing List) wrote:
> I have been experiencing a lot of the SQLITE_NOTICE(283)
This is not an emergency. You can safely ignore these warnings. I am
working to fix them for the next release, but you should not feel
pressured to take a fix right away.
--
D. Richard Hipp
Hello Fossil Devs,
After an upgrade of my local Fossil hosting executable using CGI (under
Apache 2.4.25 running on FreeBSD 10.3p16) I have been experiencing some
interesting behavior. (I am using the directory cgi-bin technique to
host my repositories.)
In the older version of Fossil that I
