Re: [fossil-users] handling backports

2015-11-05 Thread Warren Young
On Nov 4, 2015, at 1:17 AM, Andy Bradford wrote: > yabbawhap > (released in 1991) still compiles (presumably correctly), unmodified, on > a modern OpenBSD system using GCC, as do numerous other packages that > are well over 15 years old and have received no modifications. It seems like with

Re: [fossil-users] handling backports

2015-11-04 Thread Andy Bradford
Thus said Warren Young on Tue, 03 Nov 2015 15:44:04 -0700: > This isn't a LaTeX issue at all. I see substantially the same problem > with #includes on newer versions of GCC. Older versions of the code > carry a presumption about the tools used to build the code. You can't > expect

Re: [fossil-users] handling backports

2015-11-03 Thread Warren Young
On Nov 3, 2015, at 11:48 AM, Eduard wrote: > > Scenario 1: Suppose a really terrible bug (e.g. an exploitable > vulnerability) is discovered. Although the latest release is version > 2.47, it affects every version from 2.12 onwards. Trunk gets quickly > patched and

Re: [fossil-users] handling backports

2015-11-03 Thread Richard Hipp
On 11/3/15, Warren Young wrote: > On Nov 3, 2015, at 11:48 AM, Eduard wrote: >> >> Scenario 1: Suppose a really terrible bug (e.g. an exploitable >> vulnerability) is discovered. Although the latest release is version >> 2.47, it affects every

Re: [fossil-users] handling backports

2015-11-03 Thread jungle Boogie
On 3 November 2015 at 15:14, Richard Hipp wrote: > > That is exactly what --cherrypick is for. > > You can see a couple of recent examples of this in the SQLite source > tree, where we took a couple bug fixes from trunk and > cherrypick-merged them into the branch-3.9 branch to