From: Kalle <kalle@zapdevelopment.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: One recipe, two gits with destsuffix, how to patch?
Date: Tue, 19 May 2015 14:47:10 +0200 [thread overview]
Message-ID: <555B30CE.1030809@zapdevelopment.com> (raw)
In-Reply-To: <1747394.4vyzLVcRMW@peggleto-mobl5.ger.corp.intel.com>
Hi Paul,
Sorry for the late, or veeery late reply, but your suggestion here seems
to do the work.
Thanks for the help!
BR
Kalle
On 2015-01-27 11:42, Paul Eggleton wrote:
> On Tuesday 27 January 2015 10:29:12 Kalle Komierowski wrote:
>> I just modified my recipe with the patchdir.
>> SRC_URI = "
>> xxxxx.patch;patchdir=backports/
>>
>> I can see that the patches are copied to the destination where I want them
>> but for some reason they all fail when yocto tries to apply them. If I go
>> manually to the destination git and type "git am xxxxx.patch" the all apply
>> with no problem, I also tried to "patch -p1 < xxxxx.patch" and that worked
>> to. Maybe I should play a bit with the striplevel? But I do think that
>> yocto should be able to handle it from the point where I gave it the
>> patchdir=..
> The default striplevel is 1. If the patch is formatted typically, suspect this
> means that you'd need patchdir to be set to ../backports - does that not work?
>
> Cheers,
> Paul
>
prev parent reply other threads:[~2015-05-19 12:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-24 8:34 One recipe, two gits with destsuffix, how to patch? Kalle Komierowski
2015-01-26 11:04 ` Paul Eggleton
2015-01-26 11:24 ` Kalle Komierowski
2015-01-26 11:35 ` Paul Eggleton
2015-01-27 10:29 ` Kalle Komierowski
2015-01-27 10:42 ` Paul Eggleton
2015-05-19 12:47 ` Kalle [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=555B30CE.1030809@zapdevelopment.com \
--to=kalle@zapdevelopment.com \
--cc=paul.eggleton@linux.intel.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.