[oe] [meta-oe][PATCHv3] mozjs: refresh patches

Andreas Müller schnitzeltony at gmail.com
Mon Mar 26 22:27:27 UTC 2018


On Tue, Mar 27, 2018 at 12:11 AM, Martin Jansa <martin.jansa at gmail.com> wrote:
> Mostly because I find the proper patch headers useful.
>
> When doing the refresh now, I find it useful to also add original author and
> patch headers even to patches which currently apply cleanly, so that next
> time I can just use "git am foo/*" (or use git as a PATCHTOOL) and get
> usable results.
>
> I understand that it adds unnecessary changes (not needed to fix the
> WARNING), but IMHO better in separate "refresh patches" commit, than next
> time someone uses devtool for actual mozjs upgrade which might refresh the
> patches even more to make them applicable on new base version.
>
> Regards,
>
Understood - but by moving the patches devtool has created to the
original location (often they are already there) and use git add -p
you can decide for each Hunk if that is necessary or not - but it's
not that important to start a longer thread for this :)

Cheers

Andreas



More information about the Openembedded-devel mailing list