From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Bob Chen <a175818323@gmail.com>, Stefan Weil <sw@weilnetz.de>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Latest v2.12.0-rc4 has compiling error, rc3 is OK
Date: Wed, 18 Apr 2018 11:13:21 +0100 [thread overview]
Message-ID: <20180418101321.GD27579@redhat.com> (raw)
In-Reply-To: <CAFEAcA-sGiZFdAa8Gnfbo_=o-ZZbChyDJAV9oGmMTBC8BNS3sQ@mail.gmail.com>
On Wed, Apr 18, 2018 at 10:29:35AM +0100, Peter Maydell wrote:
> On 18 April 2018 at 09:09, Bob Chen <a175818323@gmail.com> wrote:
> > I found that it has nothing to do with the release version, but the github
> > one is just not able to work...
> >
> > So what github and qemu.org provide are totally different things?
>
> The "tarballs" from github don't work and can't work, but
> github provides no mechanism for the project to say "don't
> create this page". You can complain to github about this
> if you like.
>
> You're best off starting with the project's own web
> page: https://www.qemu.org/ -- we use github only as
> a sort of backup git server in case our own is down.
I sent a patch that adds a sanity check to configure to try to catch this
mistake - it would also affect people who created tarballs with a plain
"git archive" command
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 :|
next prev parent reply other threads:[~2018-04-18 10:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 6:19 [Qemu-devel] Latest v2.12.0-rc4 has compiling error, rc3 is OK Bob Chen
2018-04-18 6:25 ` Stefan Weil
2018-04-18 6:52 ` Bob Chen
2018-04-18 8:09 ` Bob Chen
2018-04-18 9:29 ` Peter Maydell
2018-04-18 9:54 ` Bob Chen
2018-04-18 10:08 ` Alex Bennée
2018-04-18 10:13 ` Daniel P. Berrangé [this message]
2018-04-18 10:06 ` Alex Bennée
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=20180418101321.GD27579@redhat.com \
--to=berrange@redhat.com \
--cc=a175818323@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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).