From: "Kalle Komierowski" <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: Mon, 26 Jan 2015 11:24:50 GMT [thread overview]
Message-ID: <1422271490695.91079.15256@webmail7> (raw)
In-Reply-To: <4306797.WdQFOdy7Io@peggleto-mobl5.ger.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1370 bytes --]
Thanks Paul!
I was hoping it was as simple as that but I couldn't find info about it. Maybe if it was just called destsuffix like when it's used for gits.
BR
-Kalle Komierowski
On January 26, 2015, Paul Eggleton <paul.eggleton@linux.intel.com> wrote:
> Hi Kalle,
>
> On Saturday 24 January 2015 08:34:56 Kalle Komierowski wrote:
> > I'm working with the ti-compat-wireless recipe.
> > It contains two gits like this:
> >
> > SRC_URI =
> > "git://git.ti.com/wilink8-wlan/wl18xx.git;branch=${BRANCH_wl18xx};destsuffi
> > x=wl18xx;name=wl18xx \
> > git://git.ti.com/wilink8-wlan/backports.git;branch=${BRANCH_backports};dest
> > suffix=backports;name=backports \ file://wl18xx.patch \
> >
> > Now I want to add the wl18xx.patch file, and this file ends up in the S and
> > applying it fails since the git it should be applied to is under
> > S/backports due to the destsuffix.
> >
> > I tried to use the quilt and create new patches from the S but they fail to.
> >
> > What would be the correct way of adding a patch so it applies to backports?
> >
> You may find the patchdir option for the patch SRC_URI entry to be useful. I
> should imagine you'll want something like:
> ...
> file://wl18xx.patch;patchdir=../backports
> ...
>
> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre
>
[-- Attachment #2.1: Type: text/html, Size: 1581 bytes --]
next prev parent reply other threads:[~2015-01-26 11:28 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 [this message]
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
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=1422271490695.91079.15256@webmail7 \
--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.