From: Richard Henderson <rth@twiddle.net>
To: "Andreas Färber" <afaerber@suse.de>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3] trivial: Remove some pre-TCG CPUArchState members
Date: Wed, 21 Nov 2012 10:23:47 -0800 [thread overview]
Message-ID: <50AD1C33.8060509@twiddle.net> (raw)
In-Reply-To: <50AD0AB3.7020207@suse.de>
On 2012-11-21 09:09, Andreas Färber wrote:
> Not sure if this fits our current Hard Freeze definition though. ;)
How often do I need to ping patches to get them applied?
I've generally been waiting 1-2 weeks between pings.
I've got at least 5 minor patch sets outstanding, dating
back to at least late September.
I hope for the next release there's both soft and hard
freeze periods, and much more help from those with commit
privs in reducing the outstanding patch queues before we
decide on "done".
r~
next prev parent reply other threads:[~2012-11-21 18:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 21:36 [Qemu-devel] [PATCH 0/3] trivial: Remove some pre-TCG CPUArchState members Richard Henderson
2012-11-01 21:36 ` [Qemu-devel] [PATCH 1/3] target-alpha: Remove t0, t1 from CPUAlphaState Richard Henderson
2012-11-01 21:36 ` [Qemu-devel] [PATCH 2/3] target-m68k: Remove t1 from CPUM68KState Richard Henderson
2012-11-01 21:36 ` [Qemu-devel] [PATCH 3/3] target-sparc: Remove t0, t1 from CPUSPARCState Richard Henderson
2012-11-21 16:51 ` [Qemu-devel] [PATCH 0/3] trivial: Remove some pre-TCG CPUArchState members Richard Henderson
2012-11-21 17:09 ` Andreas Färber
2012-11-21 18:23 ` Richard Henderson [this message]
2012-11-21 18:42 ` Peter Maydell
2012-11-22 7:57 ` [Qemu-devel] [Qemu-trivial] " Stefan Hajnoczi
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=50AD1C33.8060509@twiddle.net \
--to=rth@twiddle.net \
--cc=afaerber@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).