All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: ronnie sahlberg <ronniesahlberg@gmail.com>, Stefan Weil <sw@weilnetz.de>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Peter Lieven" <pl@kamp.de>, qemu-devel <qemu-devel@nongnu.org>,
	"Aurélien Jarno" <aurelien@aurel32.net>,
	"Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [RFC] How to handle feature regressions in new QEMU releases
Date: Wed, 16 Jul 2014 21:29:15 +0400	[thread overview]
Message-ID: <53C6B66B.1050204@msgid.tls.msk.ru> (raw)
In-Reply-To: <CAN05THSFm4nOr5aAXhBjJomwb8Dt-2dnU6GRKdDa=g_2QS3aMw@mail.gmail.com>

16.07.2014 21:23, ronnie sahlberg wrote:

> If you ask debian to upgrade. Could you ask them to wait and upgrade after I
> have release the next version, hopefully if all goes well, at the end
> of this week?

There's no problem in updating now to fix missing .pc file and to update
next week to include a new version.

Thanks,

/mjt

  reply	other threads:[~2014-07-16 17:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-16  0:26 [Qemu-devel] [ANNOUNCE] QEMU 2.1.0-rc2 is now available Michael Roth
2014-07-16 16:28 ` [Qemu-devel] [RFC] How to handle feature regressions in new QEMU releases (was: [ANNOUNCE] QEMU 2.1.0-rc2 is now available) Stefan Weil
2014-07-16 16:46   ` Peter Maydell
2014-07-16 17:37     ` [Qemu-devel] [RFC] How to handle feature regressions in new QEMU releases Peter Lieven
2014-07-16 16:49   ` Paolo Bonzini
2014-07-16 17:11     ` Stefan Weil
2014-07-16 17:23       ` ronnie sahlberg
2014-07-16 17:29         ` Michael Tokarev [this message]
2014-07-24  0:37           ` ronnie sahlberg
2014-07-24 10:10             ` Michael Tokarev
2014-07-16 17:36         ` Peter Lieven
2014-07-16 17:28       ` Michael Tokarev

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=53C6B66B.1050204@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=aurelien@aurel32.net \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=pl@kamp.de \
    --cc=qemu-devel@nongnu.org \
    --cc=ronniesahlberg@gmail.com \
    --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 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.