[fossil-users] Release version of fossil based on embedded SQLite with alpha status?
It's been a long time since there has been an official release of Fossil. This is Version 1.19. Changes in this release include: [...] - Update to the latest SQLite version 3.7.8 alpha. Hi! An official release with an embedded *alpha* version? Is this really a release version meant for production as 1.18 was? Cheers, Tino ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Release version of fossil based on embedded SQLite with alpha status?
On Mon, Sep 5, 2011 at 8:08 AM, Tino Lange tino.la...@interactivedata.comwrote: It's been a long time since there has been an official release of Fossil. This is Version 1.19. Changes in this release include: [...] - Update to the latest SQLite version 3.7.8 alpha. Hi! An official release with an embedded *alpha* version? Is this really a release version meant for production as 1.18 was? Yes. Even alpha versions of SQLite are very stable. Fossil version 1.19 is ready for production use. The version of SQLite in Fossil 1.19 went through most of our pre-release validation tests. (See http://www.sqlite.org/checklists/3070800 for details.) Alpha is just a label. Don't get hung up on it. Note that we eat our own dogfood here. The version of Fossil that runs the Fossil website (and the SQLite website) is typically the tip of trunk - even newer than the 1.19 release. Note further that we also tend to use the very latest SQLite (tip of trunk) on production code in-house. This email is being sent to you via gmail using Firefox-Nightly recompiled with the SQLite tip-of-trunk, for example. Cheers, Tino ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] CR/NL warning in .pdf
Hi, I'm wondering if this warning is OK: ./storage/exp-queue6deads-rectime-N200-s8-r3-b1000-c1_2-upbw28-mtbf1440.pdf contains CR/NL line endings; commit anyhow (yes/no/all)? While committing in a recent trunk build. I just don't know what's the story behind line endings in PDF. Kind regards, Remigiusz Modrzejewski ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] blob_zero, empty_blob and blob_reset
On Sun, Sep 04, 2011 at 10:57:27PM +0200, Lluís Batlle i Rossell wrote: On Sun, Sep 04, 2011 at 10:29:23PM +0200, Lluís Batlle i Rossell wrote: So, don't consider that branch with a working annotate. :) Anyway, I'd like someone to take a look at the heavy leaks, and to get an explanation on how to use blobs (initialise to empty_blob or not or what). Yesterday I achieved quite a working code, through the use of empty_blob (to overcome the assertion), changing some blob operations (solving some leaks), and freeing that allocated never freed. One of the fixes took me quite more work, and I'm not really happy about the final solution, although I think it works fine. I think there should be some simpler implementation. Any ideas welcome, of course. I'd be glad if someone other than me reviewed and tested the code, as I clearly touched parts that I did not know deeply. Thank you very much, Lluís. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] CR/NL warning in .pdf
On Mon, Sep 05, 2011 at 07:26:37PM +0200, Remigiusz Modrzejewski wrote: I'm wondering if this warning is OK: ./storage/exp-queue6deads-rectime-N200-s8-r3-b1000-c1_2-upbw28-mtbf1440.pdf contains CR/NL line endings; commit anyhow (yes/no/all)? While committing in a recent trunk build. I just don't know what's the story behind line endings in PDF. The problem is while PDF is considered to be a binary file (and it indeed usually contains compressed regions, it does contain ASCII header and footer (I think it's its PostScript heritage), so it can be considered to be a plain ASCII file by any tool which does not look for its special magic character sequence (in the first line of the header). Probably Fossil does not do that. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
