From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] sed invocation for keycodemapdb not portable
Date: Wed, 7 Feb 2018 14:00:37 +0000 [thread overview]
Message-ID: <20180207140037.GK32061@redhat.com> (raw)
In-Reply-To: <20180207135642.GA21399@aepfle.de>
On Wed, Feb 07, 2018 at 02:56:47PM +0100, Olaf Hering wrote:
> With commit 927128222b ("ui: add keycodemapdb repository as a GIT
> submodule") sed is called with -E, which requires a recent sed.
> The version of sed shipped with SLE11 is 4.1.5, which does not
> understand the option '-E'. As a result xen-4.11 will fail to build.
>
> Is there a way to achive the same result in some other way?
Sorry, I've got a patch queued already that fixes this, but haven't send
a pull request.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2018-02-07 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 13:56 [Qemu-devel] sed invocation for keycodemapdb not portable Olaf Hering
2018-02-07 14:00 ` Daniel P. Berrangé [this message]
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=20180207140037.GK32061@redhat.com \
--to=berrange@redhat.com \
--cc=olaf@aepfle.de \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).