From: Adrian Bunk <bunk@stusta.de>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/8] blktool: update to 4-7.1
Date: Wed, 27 Mar 2019 16:51:10 +0200 [thread overview]
Message-ID: <20190327145110.GA23257@localhost> (raw)
In-Reply-To: <20190327140922.109867-3-alex.kanavin@gmail.com>
On Wed, Mar 27, 2019 at 03:09:17PM +0100, Alexander Kanavin wrote:
> This update adds a patch from Debian to match the latest version there.
>...
> + file://0004-fix-ftbfs-glibc-2.28.patch \
> file://blktool-gnulib-makedev.patch \
>...
That's 2 patches adding the same #include.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-03-27 14:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 14:09 [PATCH 1/8] db: fix upstream version check Alexander Kanavin
2019-03-27 14:09 ` [PATCH 2/8] syslinux: " Alexander Kanavin
2019-03-27 14:09 ` [PATCH 3/8] blktool: update to 4-7.1 Alexander Kanavin
2019-03-27 14:51 ` Adrian Bunk [this message]
2019-03-27 15:05 ` Alexander Kanavin
2019-03-27 14:09 ` [PATCH 4/8] bmap-tools: fix upstream version check Alexander Kanavin
2019-03-27 14:09 ` [PATCH 5/8] sysklogd: switch SRC_URI to the new, maintained location Alexander Kanavin
2019-03-27 14:09 ` [PATCH 6/8] binutils: fix upstream version check Alexander Kanavin
2019-03-28 12:16 ` ChenQi
2019-03-28 12:08 ` Alexander Kanavin
2019-03-27 14:09 ` [PATCH 7/8] llvm: update from 8.0.0rc2 to 8.0.0 final release Alexander Kanavin
2019-03-27 14:43 ` Martin Jansa
2019-03-27 14:55 ` Alexander Kanavin
2019-03-27 14:09 ` [PATCH 8/8] sysprof: drop obsolete no-update reason Alexander Kanavin
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=20190327145110.GA23257@localhost \
--to=bunk@stusta.de \
--cc=alex.kanavin@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox