I think that the GitApplyTree patch implementation may not be quite
performing as expected when dealing with a non-default ${S} and patch
striplevels.I'm not quite sure there aren't scenarios where we *do* want to honor striplevel in GitApplyTree, even though it always appears to apply patches at the repository's root, so I wanted to send this out for feedback. The change does at least address the scenario I encountered, but there's probably a legitimate use case I'm missing where we need striplevel here. Kyle Russell (1): patch: don't strip GitApplyTree patches meta/lib/oe/patch.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) -- 2.17.1
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#137130): https://lists.openembedded.org/g/openembedded-core/message/137130 Mute This Topic: https://lists.openembedded.org/mt/72890513/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
