diff options
| author | Ross Burton <ross.burton@intel.com> | 2017-11-15 16:44:14 +0000 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2018-03-07 06:33:59 -0800 |
| commit | 453a433768bff76e4d3ad9bf40fd9d8210b0950e (patch) | |
| tree | ee3d64f9363e241b887f11576a3d51dd71884611 /oe-init-build-env | |
| parent | a9f9ca73840d1e6911e496a32ee862a724615b50 (diff) | |
| download | openembedded-core-453a433768bff76e4d3ad9bf40fd9d8210b0950e.tar.gz openembedded-core-453a433768bff76e4d3ad9bf40fd9d8210b0950e.tar.bz2 openembedded-core-453a433768bff76e4d3ad9bf40fd9d8210b0950e.zip | |
vulkan: refresh patches
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'oe-init-build-env')
0 files changed, 0 insertions, 0 deletions