<off-topic>
Hachmann wrote:
> Let's see if I can do a manual patch ...
You don't have to do that manually - jabiertxof simply mentioned that the trunk patch applies to 0.92.x as well (just with a few warnings that the changes are applied offset from the location as noted in the diff file).
Download the patch file, then first try a dry-run:
These messages are all ok (all changes succeeded, nothing failed to apply).
Now apply the patch, and then recompile.
$ patch -p0 < path-to-download/fix-bug-1657874.patch
You can later remove the changes of the patch (e.g. to prevent a potential conflict when updating the local branch after a final version of the fix was committed):
$ patch -p0 --dry-run -R < path-to-download/fix-bug-1657874.patch
$ patch -p0 -R < path-to-download/fix-bug-1657874.patch
<off-topic>
Hachmann wrote:
> Let's see if I can do a manual patch ...
You don't have to do that manually - jabiertxof simply mentioned that the trunk patch applies to 0.92.x as well (just with a few warnings that the changes are applied offset from the location as noted in the diff file).
Download the patch file, then first try a dry-run:
$ patch -p0 --dry-run < path-to- download/ fix-bug-1657874.patch drag.cpp
checking file src/gradient-
checking file src/gradient-drag.h
checking file src/knot.cpp
Hunk #1 succeeded at 229 (offset 15 lines).
Hunk #2 succeeded at 256 (offset 15 lines).
Hunk #3 succeeded at 294 (offset 18 lines).
checking file src/knot.h
$
These messages are all ok (all changes succeeded, nothing failed to apply).
Now apply the patch, and then recompile. download/ fix-bug-1657874.patch
$ patch -p0 < path-to-
You can later remove the changes of the patch (e.g. to prevent a potential conflict when updating the local branch after a final version of the fix was committed): download/ fix-bug-1657874.patch download/ fix-bug-1657874.patch
$ patch -p0 --dry-run -R < path-to-
$ patch -p0 -R < path-to-
</off-topic>