Linus Torvalds writes: (Summary) I looked at the patch and it looked "obviously correct", but only
tested my current tree (which had the above fix), not that actual
tree.
tree.
Heh. git apply is actually very careful and refuses to apply with fuzz, but yes, it will apply with a big offset if the original place has changed and it can find another place that is an exact match (why? Think "somebody moved code around").
Think "somebody moved code around").
But yeah, apparently that _right_ point had changed, and there was an exact match at the wrong spot.
tree.
[...]
I blame git apply for being a bit overzealous.Heh. git apply is actually very careful and refuses to apply with fuzz, but yes, it will apply with a big offset if the original place has changed and it can find another place that is an exact match (why? Think "somebody moved code around").
Think "somebody moved code around").
But yeah, apparently that _right_ point had changed, and there was an exact match at the wrong spot.