Thank you for releasing a new tagged release to pick up the various php 7.2 compatibility fixes of recent months.
Regarding #2742913: Warning and notice from line 247
A patch at #2742913-5: Warning and notice from line 247 was committed, and the issue marked as Closed (Fixed).
Subsequently, another problem was found, caused by fixing it in that way, resulting in a better patch at #2742913-11: Warning and notice from line 247
I had manually applied that patch to my site, and it worked. Having downloaded 7.x-3.8, I checked that patch would suggest reversal if I tried to apply that same patch, but to my surprise it didn't. So I then noticed what I'd missed before - because #2742913: Warning and notice from line 247 was never reopened, the patch at #2742913-11: Warning and notice from line 247 was never committed.
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | context-n3014980-7.patch | 1.12 KB | damienmckenna |
| #8 | context-n3014980-7.interdiff.txt | 988 bytes | damienmckenna |
Comments
Comment #2
jamesoakleyAttached is the patch you get if you start with the context.module file from the latest tagged release, apply patch 5 in reverse and then apply patch 11. So applying this to the current state will get you, in one move, to where you'd need to be if you'd run patch 11 instead.
Comment #4
jamesoakleyWrongly formatted patch file header. Try again
Comment #6
jamesoakleyAlright, I give up: I'll use "git diff" instead of diff-utils diff.
Comment #7
jamesoakleyOK, now the test suite can actually parse the patch file, it's passed. Given this is nothing more than a re-roll of a patch in the related issue which has been reviewed and found to work, I'll set this back to RTBC.
Comment #8
damienmckennaA minor tweak to add a period at the end of the sentence :)
A small reminder - you shouldn't RTBC your own patch, please leave it for others to review.
Comment #9
damienmckennaComment #10
damienmckennaComment #12
nedjoCrediting Andrey Inkin for the patch at #2742913-11: Warning and notice from line 247.
Comment #14
nedjoComment #15
nedjoThanks for catching this and pointing to the fix.