From: Jeff Cody <jcody@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: John Snow <jsnow@redhat.com>,
qemu-devel@nongnu.org, kwolf@redhat.com,
peter.maydell@linaro.org, berrange@redhat.com,
qemu-block@nongnu.org, mreitz@redhat.com, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v3 for-2.10 0/4] improved --version/--help tweaks
Date: Tue, 8 Aug 2017 10:15:16 -0400 [thread overview]
Message-ID: <20170808141516.GH1525@localhost.localdomain> (raw)
In-Reply-To: <70c58145-ab14-a9b5-69d4-4bf39cc180af@redhat.com>
On Tue, Aug 08, 2017 at 08:50:55AM -0500, Eric Blake wrote:
> On 08/07/2017 07:08 PM, John Snow wrote:
> >
> >
> > On 08/03/2017 12:33 PM, Eric Blake wrote:
> >> Not sure if this should go through Kevin's block tree, Paolo's
> >> miscellaneous patches, or if I should just do a pull request
> >> myself (since patch 4 includes a change to qemu-nbd)
> >>
>
> >
> > Nothing to keep the commands from going out of order again, it looks
> > like -- can this be added as a comment or otherwise scripted as a
> > ./hey_it_looks_like_you_are_about_to_release_qemu.sh script that makes
> > sure we've dotted the 'i's and crossed the 't's?
>
> We don't add subcommands to qemu-img all that frequently; I think a
> comment is okay without having to figure out where to script things.
>
> >
> > Lastly, Didn't we fix the certificate issue? (I thought Jeff had) -- and
> > even if not, it's still the correct address to send people to IMO. Let
> > people report to us if the SSL certificate appears to be broken.
>
> That can be a followup-patch.
>
Probably no need for one, really. We force redirect to SSL, so the http://
versions will still end up https://.
And to confirm - the SSL certificates are now all in order. The issue on
the website I think you were referencing in that commit message is because
we still had two URL resources pulling in non-ssl assets (Google fonts, and
jquery), so browsers blocked those mixed requests. But that has been
updated.
-Jeff
prev parent reply other threads:[~2017-08-08 14:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 16:33 [Qemu-devel] [PATCH v3 for-2.10 0/4] improved --version/--help tweaks Eric Blake
2017-08-03 16:33 ` [Qemu-devel] [PATCH v3 1/4] qemu-img: Sort sub-command names in --help Eric Blake
2017-08-03 16:33 ` [Qemu-devel] [PATCH v3 2/4] qemu-io: Give more --version information Eric Blake
2017-08-03 16:33 ` [Qemu-devel] [PATCH v3 3/4] qga: " Eric Blake
2017-08-03 16:33 ` [Qemu-devel] [PATCH v3 4/4] maint: Include bug-reporting info in --help output Eric Blake
2017-08-08 0:08 ` [Qemu-devel] [Qemu-block] [PATCH v3 for-2.10 0/4] improved --version/--help tweaks John Snow
2017-08-08 13:50 ` Eric Blake
2017-08-08 14:15 ` Jeff Cody [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=20170808141516.GH1525@localhost.localdomain \
--to=jcody@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.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 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).