Quote:
Originally Posted by hawhill
|
Is that one based on the 2014-11-11 with the just discussed bug fixed?
I have to ask, since that bug is not listed at that link as either open or closed.
Edit:
Pull the 2014-11 stable tagged code, see if it has the "has fake events" commit included.
Could be that the bug was newer and fixed more recently than that 2014-11 stable page was generated.
Edit-2:
Ah, I see part of the problem, the repo does not have a v2014.11-stable tag point.
The most recent 'stable' tag is the 2014.04-stable tag.
Where-as the problem just discussed was merged at the v2014.11.11-nightly tag point.
ah, hell, what's just 7 months of bug-fix cherry picking among friends?
it isn't any harder than shuffling the deck chairs on the Titanic.
- - - - -
I got it now:
pull the 2014.11-stable tarball ;
bi-sect repo changes to find the commit closest in code to tarball contents;
move all deck chairs from starboard to port side (so no one sees ice burg coming);
(where "it" is one possible path to backport bug fixes **only** since 2014.11-stable.)