From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: Stefan Hajnoczi <stefanha@gmail.com>,
Anthony Liguori <aliguori@amazon.com>
Cc: "Michael Tokarev" <mjt@tls.msk.ru>,
"Laszlo Ersek" <lersek@redhat.com>,
"Andreas Färber" <afaerber@suse.de>,
"qemu devel list" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] please release qemu version 1.7.1
Date: Tue, 25 Mar 2014 09:13:05 -0500 [thread overview]
Message-ID: <20140325141305.22831.17037@loki> (raw)
In-Reply-To: <20140325123838.GA29231@stefanha-thinkpad.redhat.com>
Quoting Stefan Hajnoczi (2014-03-25 07:38:38)
> On Mon, Mar 24, 2014 at 10:59:42PM +0100, Laszlo Ersek wrote:
> > On 03/24/14 22:50, Andreas Färber wrote:
> > > Laszlo,
> > >
> > > Am 24.03.2014 20:23, schrieb Laszlo Ersek:
> > >> http://wiki.qemu.org/Planning/1.7
> > >>
> > >> Thank you.
> > >> Laszlo
> > >
> > > Since you're not addressing anyone in particular who could create the
> > > release for you, the tag already exists on Michael's branch:
> > > https://github.com/mdroth/qemu/commits/v1.7.1
> > >
> > > And you can use scripts/make-release as an interim solution for creating
> > > the tarball from it.
> >
> > Thank you. However, I don't need the release for myself. I'd like to
> > submit an OVMF patch (ACPI table download). That patch causes an OVMF
> > regression when running on v1.7.0, but works on v1.7.1 (and of course on
> > 2.0.0-rc0). I'd like the tarball to be available to users; both to
> > people who download it from the upstream location, and to those who use
> > 1.7.x-based distro (eg. Debian) packages.
> >
> > In my OVMF patch I'd like to reference the v1.7.1 qemu release.
> >
> > (Side note, the patch is also fine on v1.6.x and earlier.)
> >
> > > If you do, you might be interested in:
> > > http://patchwork.ozlabs.org/patch/331939/
> > >
> > > What's missing is someone who can upload the tarball and edit all
> > > relevant Wiki pages. And someone to push branch and tag to qemu.git.
> >
> > "Can" as in "is willing", or as in "is permitted"?
> >
> > I didn't know whom to address specifically.
>
> Anthony is doing releases and is the right person to poke.
>
> I think all that's left is publishing the tarball and posting the
> release announcement.
Yes, Anthony was tied up around release time and I was subsequently out for
a couple weeks due to a family emergency so didn't have a chance to follow-up
till late last week. I'll do the announce as soon as we get the tarball
uploaded. I'm still used to being able to walk next door, need to coordinate
in advance a bit better next time.
>
> Stefan
next prev parent reply other threads:[~2014-03-25 14:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 19:23 [Qemu-devel] please release qemu version 1.7.1 Laszlo Ersek
2014-03-24 21:50 ` Andreas Färber
2014-03-24 21:59 ` Laszlo Ersek
2014-03-25 8:34 ` Gerd Hoffmann
2014-03-25 12:38 ` Stefan Hajnoczi
2014-03-25 14:13 ` Michael Roth [this message]
2014-03-25 14:16 ` Anthony Liguori
2014-03-25 15:28 ` Andreas Färber
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=20140325141305.22831.17037@loki \
--to=mdroth@linux.vnet.ibm.com \
--cc=afaerber@suse.de \
--cc=aliguori@amazon.com \
--cc=lersek@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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 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).