From: <Mikko.Rapeli@bmw.de>
To: <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] busybox.inc: handle empty DEBUG_PREFIX_MAP
Date: Mon, 16 Sep 2019 12:43:05 +0000 [thread overview]
Message-ID: <20190916124304.GP6154@hiutale> (raw)
In-Reply-To: <71c210c6-abf0-4c0c-06b6-1a7bf01279e7@intel.com>
Hi,
On Mon, Sep 16, 2019 at 01:37:25PM +0100, Ross Burton wrote:
> Hi Mikko,
>
> This is 1/2 but 2/2 never arrived on the list. Can you repost it?
Sorry, 2/2 from my poky tree was the bitbake svn fetcher patch in
http://lists.openembedded.org/pipermail/bitbake-devel/2019-September/020328.html
Can you ignore the numberings or shall I send again without them?
-Mikko
next prev parent reply other threads:[~2019-09-16 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 7:16 [PATCH 1/2] busybox.inc: handle empty DEBUG_PREFIX_MAP Mikko Rapeli
2019-09-16 12:37 ` Ross Burton
2019-09-16 12:43 ` Mikko.Rapeli [this message]
2019-09-16 12:47 ` Ross Burton
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=20190916124304.GP6154@hiutale \
--to=mikko.rapeli@bmw.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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 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.