From: Eric Blake <eblake@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Andrew Jones <drjones@redhat.com>
Cc: wei@redhat.com, peter.maydell@linaro.org, qemu-devel@nongnu.org,
peterx@redhat.com, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] tests/migration: Add source to PC boot block
Date: Mon, 12 Feb 2018 10:32:07 -0600 [thread overview]
Message-ID: <cbbf1a55-33ec-2738-62f9-b7a7c531941f@redhat.com> (raw)
In-Reply-To: <20180212150703.GB2545@work-vm>
On 02/12/2018 09:07 AM, Dr. David Alan Gilbert wrote:
>>
>> Is xxd now considered a common enough tool for portable scripts? I've
>> always liked xxd for manual use, but scripted with 'od'.
>
> This script isn't part of a normal build or make check or anything, so
> jumping through hoops to make it portable for the mythical other person
> who might ever run it seems OTT, especially since xxd is very common,
> and I'm not sure how much I'd bet on the portability of od's output
> format either.
Relying on xxd is okay given your arguments, but od IS portable (it is
required by POSIX, and if you stick to the basics that POSIX documents,
things are pretty consistent between implementations). I will grant,
however, that a portable use of od has a much longer command line (with
the options you need to turn on for saner output, because who reads
octal these days) than xxd giving you hex by default.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
prev parent reply other threads:[~2018-02-12 16:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 18:18 [Qemu-devel] [PATCH v2] tests/migration: Add source to PC boot block Dr. David Alan Gilbert (git)
2018-02-09 21:47 ` Wei Huang
2018-02-12 13:32 ` Andrew Jones
2018-02-12 15:07 ` Dr. David Alan Gilbert
2018-02-12 16:14 ` Wei Huang
2018-02-12 16:32 ` Eric Blake [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=cbbf1a55-33ec-2738-62f9-b7a7c531941f@redhat.com \
--to=eblake@redhat.com \
--cc=dgilbert@redhat.com \
--cc=drjones@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=wei@redhat.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.