From: Henning Schild <henning.schild@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Baurzhan Ismagulov <ibr@radix50.net>, <isar-users@googlegroups.com>
Subject: Re: [PATCH] lib/oe/path: try hardlinking instead of guessing when it might fail
Date: Mon, 6 Apr 2020 12:03:47 +0200 [thread overview]
Message-ID: <20200406120347.4625b204@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <345b97fd-c9ee-e4de-2251-1861cb05a311@siemens.com>
On Mon, 6 Apr 2020 09:51:23 +0200
Jan Kiszka <jan.kiszka@siemens.com> wrote:
> On 06.04.20 09:42, Henning Schild wrote:
> > On Sun, 5 Apr 2020 18:58:16 +0200
> > Baurzhan Ismagulov <ibr@radix50.net> wrote:
> >
> >> Hello Henning,
> >>
> >> On Fri, Jan 24, 2020 at 02:51:00PM +0100, Henning Schild wrote:
> >>> This is related to fixing an issue with "--exclude-path" in wic.
> >>> On the Isar side i have everything in place and might send it.
> >>> But we need that upstream fix ... or some workaround if that does
> >>> not get merged.
> >>
> >> Do I understand correctly, you'd be providing a lib/oe update for
> >> Isar along with the other necessary changes? A test case for
> >> --exclude-path would be nice.
> >
> > The test-case is already somewhere in a branch of mine ;). The
> > problem now is that this upstream fix need to come down into Isar.
> >
> > But i am afraid that our lib/oe is a fork, miles away from
> > upstream.
>
> We are fairly close, picking patches from upstream is often possible
> when we aren't. I just did that not long ago
> (9813e9e821cb2c4f0ea66544e35030fa261f1a47). Some bits may have to
> remain different sometimes, though.
Ok, i will try a backport and send that test-case along with it.
Henning
> Jan
>
next prev parent reply other threads:[~2020-04-06 10:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 13:48 Henning Schild
2020-01-24 13:51 ` Henning Schild
2020-02-18 19:24 ` Henning Schild
2020-04-05 16:58 ` Baurzhan Ismagulov
2020-04-06 7:42 ` Henning Schild
2020-04-06 7:51 ` Jan Kiszka
2020-04-06 10:03 ` Henning Schild [this message]
2020-04-06 20:20 ` Henning Schild
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=20200406120347.4625b204@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=ibr@radix50.net \
--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