2014/1/14 Jan Nijtmans <jan.nijtm...@gmail.com>:
> And the last one which doesn't affect fossil
> at all because fossil doesn't use fork():
>     <https://www.mail-archive.com/sqlite-users@sqlite.org/msg81284.html>
>
> Branch "branch-1.28" currently contains SQLite 3.8.2
> with 5 additional bug-fixes: All the ones mentioned
> above except the last one.

A small status update: Fossil's "branch-1.28"
contains a new SQLite amalgalation now,
constructed from SQLite's "branch-3.8.2".
This SQLite branch contains all bug-fixes
I mentioned, including the 6'th one (which
actually doesn't affect fossil). No bug-fixes
appeared in SQLite trunk after that, so
it appears there is full agreement on
where the most STABLE SQLite version
can be found at this moment:
    <http://www.sqlite.org/cgi/src/timeline?r=branch-3.8.2>

Some bug-fixes appeared in Fossil's trunk, the most
important ones are collected here by Joe Mistachkin:
     <http://www.fossil-scm.org/fossil/info/76442af7e1>
In my view, there are two more "Nice-To-Haves" which
are well-enough tested (and evaluated) to be included
in the 1.28 release as well. Those are:
   <http://www.fossil-scm.org/fossil/info/b4dffdac5e>
and:
   <http://www.fossil-scm.org/fossil/info/ab00f2b007>
They are not crucial. I'll leave it to Richard's judgement
whether they should be included or not. I'll be a happy
person either way.

Thanks for all feedback so far.....

Regards,
        Jan Nijtmans
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to