From: Markus Armbruster <armbru@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Markus Armbruster <armbru@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Keno Fischer <keno@juliacomputing.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>, Greg Kurz <groug@kaod.org>
Subject: Re: [Qemu-devel] [PATCH v4] cutils: Provide strchrnul
Date: Wed, 13 Jun 2018 07:50:44 +0200 [thread overview]
Message-ID: <87tvq7kzez.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <CAFEAcA9XiuToz7pCEOysL-Hz1HvVyaMyeXV-yJi1xpHgdycLiw@mail.gmail.com> (Peter Maydell's message of "Mon, 11 Jun 2018 09:52:55 +0100")
Peter Maydell <peter.maydell@linaro.org> writes:
> On 11 June 2018 at 08:56, Markus Armbruster <armbru@redhat.com> wrote:
>> You're not printing $strchrnul like we print other configuration
>> results. Hmm, we're not printing several of them. Question for
>> maintainers (MAINTAINERS doesn't have any, so I'm cc'ing the top three
>> coughed up by get_maintainer.pl): bug or feature? If feature, how do we
>> decide what to print?
>
> If we printed everything that we tested for then the output would
> be unhelpfully enormous. My view is that we should print the
> "interesting" things for the user, ie the higher-level things
> that the user could potentially turn on by installing more
> libraries or has turned off explicitly or whatever. Reporting
> whether the host OS has strchrnul or whether we've had to
> provide our own implementation is doubly uninteresting:
> * there's nothing the user could do to change this
> * there is no visible effect (missing features, worse performance)
Care to clean out out existing "uninteresting" prints?
> There's an argument that we should also log every config check
> result somehow (I think autoconf configures do this), but I
> don't think that our 'print stuff to stdout' is the right place
> for that.
Makes sense. Volunteers?
next prev parent reply other threads:[~2018-06-13 5:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-10 18:02 [Qemu-devel] [PATCH v4] cutils: Provide strchrnul Keno Fischer
2018-06-11 7:56 ` Markus Armbruster
2018-06-11 8:52 ` Peter Maydell
2018-06-11 9:33 ` Dr. David Alan Gilbert
2018-06-11 9:38 ` Daniel P. Berrangé
2018-06-11 10:11 ` Peter Maydell
2018-06-13 5:50 ` Markus Armbruster [this message]
2018-06-11 20:44 ` Keno Fischer
2018-06-12 7:07 ` Markus Armbruster
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=87tvq7kzez.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=groug@kaod.org \
--cc=keno@juliacomputing.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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 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.