From: "Andriy Danylovskyy" <andriy.danylovskyy@streamunlimited.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] classes/patch: move QUILT_PC for patching consistency
Date: Mon, 26 Sep 2022 05:59:02 -0700 [thread overview]
Message-ID: <18402.1664197142886667457@lists.openembedded.org> (raw)
In-Reply-To: <d2e8e257c5e15ee3e91017a425a09f730c66f326.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 806 bytes --]
On 26/09/2022 14:21, Richard Purdie wrote:
>
> I'm old school and have used quilt for patching kernels for a couple of
> decades and have used it before devtool (or even git) existed! There
> are
> probably better ways now but quilt is muscle memory.
>
>
>> Then another (dirtier?) option would be to patch quilt-native
>> itself,
>> setting QUILT_PC to the relative ./patches/.pc
>>
>
> Sadly it doesn't help my use case as I'm used to changing to some
> random
> WORKDIR and using the host's copy of quilt to save messing with
> PATH :/.
>
> Cheers,
>
> Richard
>
I see, you never imagine all use cases until you ask.
But the issue needs a solution, one way or another. What's especially bad is this can go unnoticed for quite a while.
--
Best regards,
Andriy
[-- Attachment #2: Type: text/html, Size: 1051 bytes --]
prev parent reply other threads:[~2022-09-26 12:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 9:06 [PATCH] classes/patch: move QUILT_PC for patching consistency Andriy Danylovskyy
2022-09-26 9:13 ` Andriy Danylovskyy
2022-09-26 11:21 ` [OE-core] " Martin Jansa
2022-09-26 12:48 ` Andriy Danylovskyy
2022-09-26 10:23 ` [OE-core] " Richard Purdie
2022-09-26 11:46 ` Andriy Danylovskyy
2022-09-26 12:21 ` [OE-core] " Richard Purdie
2022-09-26 12:59 ` Andriy Danylovskyy [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=18402.1664197142886667457@lists.openembedded.org \
--to=andriy.danylovskyy@streamunlimited.com \
--cc=openembedded-core@lists.openembedded.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.