qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Peter Maydell <peter.maydell@linaro.org>,
	Peter Crosthwaite <crosthwaitepeter@gmail.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	"Jason Wang" <jasowang@redhat.com>,
	"Michael Tokarev" <mjt@tls.msk.ru>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Michael Roth" <mdroth@linux.vnet.ibm.com>,
	"Max Filippov" <jcmvbkbc@gmail.com>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"Juan Quintela" <quintela@redhat.com>,
	"Alexander Graf" <agraf@suse.de>,
	"Christian Borntraeger" <borntraeger@de.ibm.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Richard Henderson" <rth@twiddle.net>,
	"Leon Alrae" <leon.alrae@imgtec.com>,
	"Jeff Cody" <jcody@redhat.com>,
	"Laurent Vivier" <lvivier@redhat.com>,
	"Eduardo Habkost" <ehabkost@redhat.com>,
	"Stefano Stabellini" <stefano.stabellini@eu.citrix.com>,
	"Stefan Weil" <sw@weilnetz.de>,
	"Riku Voipio" <riku.voipio@iki.fi>,
	"Alex Williamson" <alex.williamson@redhat.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Cornelia Huck" <cornelia.huck@de.ibm.com>,
	"John Snow" <jsnow@redhat.com>,
	"David Gibson" <david@gibson.dropbear.id.au>,
	"Kevin Wolf" <kwolf@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Max Reitz" <mreitz@redhat.com>,
	"Amit Shah" <amit.shah@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Andreas Färber" <afaerber@suse.de>,
	"Aurelien Jarno" <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] Reminder: we're now in softfreeze
Date: Mon, 26 Oct 2015 09:56:02 +0000	[thread overview]
Message-ID: <562DF8B2.1040207@ilande.co.uk> (raw)
In-Reply-To: <CAFEAcA92HK0tSARXZj9iQqpQmYU=WeJpr12UTEQaSyKkSm2dFQ@mail.gmail.com>

On 26/10/15 09:27, Peter Maydell wrote:

> On 26 October 2015 at 06:25, Peter Crosthwaite
> <crosthwaitepeter@gmail.com> wrote:
>> On Thu, Oct 22, 2015 at 3:30 AM, Peter Maydell <peter.maydell@linaro.org> wrote:
>>> For this release I'd like to try tracking known-issues on
>>> the wiki page: http://wiki.qemu.org/Planning/2.5
>>> with a list of patch series or bugs which need to be fixed
>>> into the release. This will hopefully avoid the problem we
>>> had last time around where I missed patches that should have
>>> gone into an rc.
>>
>> Can patches fix this with the right form of query? Maybe another piece
>> of metadata for patches that are promoted for rc merge.
> 
> ...only if the submitter remembers to tag it when they send
> it, and it doesn't help for issues that don't have a patch yet,
> or for tracking whether a submaintainer has taken the patch.
> 
> Tagging your patch as "[PATCH for-2.5]" is a good idea anyway
> once we're in freeze, though.

Maybe we also need a [PING for-2.5] or similar? I've just sent another
couple of pings for patches (one of which fixes the broken
analyze-migration.py script) which have fallen through the cracks over
the past couple of months. It would be nice to have an easy way to flag
outstanding patches like this, especially during freeze when things get
really busy.


ATB,

Mark.

  reply	other threads:[~2015-10-26  9:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-22 10:30 [Qemu-devel] Reminder: we're now in softfreeze Peter Maydell
2015-10-26  6:12 ` Amit Shah
2015-10-26  6:25 ` Peter Crosthwaite
2015-10-26  9:27   ` Peter Maydell
2015-10-26  9:56     ` Mark Cave-Ayland [this message]
2015-10-26 10:01       ` Peter Maydell
2015-10-26 10:10         ` Mark Cave-Ayland
2015-10-26 15:22     ` Peter Crosthwaite

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=562DF8B2.1040207@ilande.co.uk \
    --to=mark.cave-ayland@ilande.co.uk \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=alex.williamson@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=armbru@redhat.com \
    --cc=aurelien@aurel32.net \
    --cc=borntraeger@de.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=crosthwaitepeter@gmail.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=ehabkost@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=jcmvbkbc@gmail.com \
    --cc=jcody@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=leon.alrae@imgtec.com \
    --cc=lvivier@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=mjt@tls.msk.ru \
    --cc=mreitz@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=riku.voipio@iki.fi \
    --cc=rth@twiddle.net \
    --cc=stefanha@redhat.com \
    --cc=stefano.stabellini@eu.citrix.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 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).