From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>,
jpewhacker@gmail.com, Paul Barker <pbarker@konsulko.com>
Subject: Re: [OE-core] [PATCH v2 1/2] wic: Fix permissions when using exclude or include path
Date: Sun, 05 Apr 2020 16:29:44 +0100 [thread overview]
Message-ID: <db5856cec86de82a4feddf1cf739ce7eb37c6932.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAPybu_2LZgaDFL-jexc0DcnEb0nzsLpZq30nA4UNufztDsKs1w@mail.gmail.com>
On Sun, 2020-04-05 at 14:01 +0200, Ricardo Ribalda Delgado wrote:
> Ups, wrong version
>
> This is the one, sorry.
It didn't build unfortunately:
https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/837
Cheers,
Richard
next prev parent reply other threads:[~2020-04-05 15:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 14:49 [PATCH v2 1/2] wic: Fix permissions when using exclude or include path Ricardo Ribalda Delgado
2020-03-04 14:49 ` [PATCH v2 2/2] wic: Add --embed-rootfs argument Ricardo Ribalda Delgado
2020-03-05 9:33 ` Paul Barker
2020-03-05 12:26 ` Ricardo Ribalda Delgado
2020-04-03 19:52 ` Ricardo Ribalda
2020-04-07 17:47 ` Paul Barker
2020-04-07 18:19 ` Ricardo Ribalda
[not found] ` <16039C80250EF791.10037@lists.openembedded.org>
2020-04-08 10:28 ` [OE-core] " Ricardo Ribalda
2020-04-05 7:01 ` [OE-core] [PATCH v2 1/2] wic: Fix permissions when using exclude or include path Richard Purdie
2020-04-05 7:21 ` Ricardo Ribalda
[not found] ` <1602DB74B6717A3F.2403@lists.openembedded.org>
2020-04-05 9:56 ` Ricardo Ribalda
2020-04-05 11:04 ` Richard Purdie
2020-04-05 11:53 ` Ricardo Ribalda
2020-04-05 12:01 ` Ricardo Ribalda
2020-04-05 15:29 ` Richard Purdie [this message]
2020-04-05 15:44 ` Ricardo Ribalda
2020-04-06 9:00 ` Richard Purdie
2020-04-06 9:03 ` Ricardo Ribalda
[not found] ` <16032F9D180FD5D7.1684@lists.openembedded.org>
2020-04-06 9:21 ` Ricardo Ribalda
2020-04-06 13:48 ` Richard Purdie
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=db5856cec86de82a4feddf1cf739ce7eb37c6932.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=jpewhacker@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pbarker@konsulko.com \
--cc=ricardo.ribalda@gmail.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