Commit fc7ac83
1 parent a2b82bf commit fc7ac83
1 file changed
+2
-1
lines changedLines changed: 2 additions & 1 deletion
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
744 | 744 |
| |
745 | 745 |
| |
746 | 746 |
| |
747 |
| - | |
| 747 | + | |
| 748 | + | |
748 | 749 |
| |
749 | 750 |
| |
750 | 751 |
| |
|
1 parent a2b82bf commit fc7ac83
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
744 | 744 |
| |
745 | 745 |
| |
746 | 746 |
| |
747 |
| - | |
| 747 | + | |
| 748 | + | |
748 | 749 |
| |
749 | 750 |
| |
750 | 751 |
| |
|
6 commit comments
gioman commentedon Jul 24, 2017
@jef-n was this backported to 2.18?
jef-n commentedon Jul 24, 2017
No, 2.18 was not affected by this. See 9a6235d#commitcomment-23071479
gioman commentedon Jul 24, 2017
sorry, 2.18.10/11 are very much affected by this.
jef-n commentedon Jul 24, 2017
As said the line re-added in this commit wasn't removed from 2.18 - so it can't possibly affect 2.18.
gioman commentedon Jul 24, 2017
@jef ok ill try to be more precise: issues #16811 and #16819 were reported against 2.18.10 as regressions from 2.18.9 so this commit could not possibly close them, so they were reopened and the issues still affect 2.18.11
jef-n commentedon Jul 24, 2017
@gioman no need to get more precise here - and the comment referenced above already confirms that it's not a fix.