https://bz.apache.org/ooo/show_bug.cgi?id=125699
dam...@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest|--- |4.2.0-dev
Confirmation in| |
CC| |dam...@apache.org
--- Comment #7 from dam...@apache.org ---
Fortunately by now I have a large number of precompiled trunk versions from
different dates, that can be tested easily:
4.1.13 - works
latest trunk - regression
6dd50e53129adaa307ec5b2aba73acd299ab2e3b (2014-10-21) - regression
f331e23ffae9e26f93997dc8f02086c5733e80df (2014-02-25) - works
So the regression happened within the trunk branch some time during 2014,
between February and October.
$ git rev-list
f331e23ffae9e26f93997dc8f02086c5733e80df..6dd50e53129adaa307ec5b2aba73acd299ab2e3b
|wc -l
385
385 possible commits!
$ git rev-list
f331e23ffae9e26f93997dc8f02086c5733e80df..6dd50e53129adaa307ec5b2aba73acd299ab2e3b
sw |wc -l
66
66 commits to "StarWriter".
There were many changes that could have caused this.
A git bisect may be the only way to narrow this down further.
--
You are receiving this mail because:
You are the assignee for the issue.
