From: Alexander Smirnov <asmirnov@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH 1/2] Add basic patch support
Date: Tue, 20 Feb 2018 14:12:01 +0300 [thread overview]
Message-ID: <4a2e08c0-a483-3469-2466-1aadbc51218c@ilbers.de> (raw)
In-Reply-To: <389542c1-1367-2639-a13c-ebbb9318c05b@siemens.com>
On 02/18/2018 10:39 PM, Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> Add a do_patch task after unpack the processes .patch files in the
> SRC_URI. We likely miss some special features compared to OE, but this
> covers the common case of few individual patches. Application order is
> derived from appearance in SRC_URI list. Strip level can be configured
> via "striplevel=N" URI parameter. The application is controlled
> explicitly via the "apply=yes|no" parameter.
What's the issue to take the full implementation from OE? How this
user-interface differs from OE?
Alex
next prev parent reply other threads:[~2018-02-20 11:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-18 19:39 Jan Kiszka
2018-02-18 19:40 ` [PATCH 2/2] example-app: Add two patches for demonstration and testing purposes Jan Kiszka
2018-02-20 11:12 ` Alexander Smirnov [this message]
2018-02-21 9:36 ` [PATCH 1/2] Add basic patch support Jan Kiszka
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=4a2e08c0-a483-3469-2466-1aadbc51218c@ilbers.de \
--to=asmirnov@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox