From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Jes Sorensen <Jes.Sorensen@redhat.com>,
qemu-devel@nongnu.org, stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH v2] qemu-img: Initial progress printing support
Date: Fri, 22 Apr 2011 14:37:26 +0200 [thread overview]
Message-ID: <4DB17686.2010502@redhat.com> (raw)
In-Reply-To: <AANLkTi=Ge5NjMsYxbDNifRkf+XARZhexoPU56Ra2pNdr@mail.gmail.com>
On 04/01/2011 04:58 PM, Stefan Hajnoczi wrote:
> On Fri, Apr 1, 2011 at 2:41 PM, Jes Sorensen<Jes.Sorensen@redhat.com> wrote:
>> On 03/31/11 13:49, Stefan Hajnoczi wrote:
>>> On Thu, Mar 31, 2011 at 12:38 PM, Kevin Wolf<kwolf@redhat.com> wrote:
>>>> Am 31.03.2011 13:15, schrieb Jes Sorensen:
>>>>> On 03/31/11 12:38, Kevin Wolf wrote:
>>>>> I have been a little reluctant to do this because it will break the ABI
>>>>> for tools running qemu-img from a GUI etc.
>>>>
>>>> That's the reason for the "from a terminal" part. If we check for
>>>> isatty(), we should handle these cases just fine.
>>>
>>> Yes, I think checking for a tty is enough precaution and allows users
>>> to get the benefit of the progress bar. TBH I'd probably forget to
>>> add -p half the time :).
>>
>> Ok, this is fine with me - however how do you suggest we offer the
>> option to disable it on the command line, an additional flag?
If you also check stdout/stderr for isatty (probably the progress output
should go to stderr), "> /dev/null" is enough.
Paolo
prev parent reply other threads:[~2011-04-22 12:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 12:16 [Qemu-devel] [PATCH v2] qemu-img: Initial progress printing support Jes.Sorensen
2011-03-30 12:27 ` Stefan Hajnoczi
2011-03-31 10:38 ` [Qemu-devel] " Kevin Wolf
2011-03-31 11:15 ` Jes Sorensen
2011-03-31 11:38 ` Kevin Wolf
2011-03-31 11:49 ` Stefan Hajnoczi
2011-04-01 13:41 ` Jes Sorensen
2011-04-01 14:58 ` Stefan Hajnoczi
2011-04-22 12:37 ` Paolo Bonzini [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=4DB17686.2010502@redhat.com \
--to=pbonzini@redhat.com \
--cc=Jes.Sorensen@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@linux.vnet.ibm.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.