From: Anthony Liguori <aliguori@us.ibm.com>
To: Stefan Weil <weil@mail.berlios.de>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [BUG] [PATCH] [STABLE] Fix monitor command (screendump)
Date: Tue, 24 Mar 2009 16:47:13 -0500 [thread overview]
Message-ID: <49C954E1.5030706@us.ibm.com> (raw)
In-Reply-To: <49C953E2.8090702@mail.berlios.de>
Stefan Weil wrote:
> Hello,
>
> starting with r6839, the monitor command 'screendump'
> raises a nullpointer memory access which crashs Qemu.
>
> My patch fixes this for trunk and for the stable branch.
>
r6839 is not in stable so the patch isn't needed for stable.
> Regards
>
> Stefan
>
> PS. There are a lot of unapplied patches (not only from me)
> which really should be applied to trunk. Much time and efforts
> are wasted for maintaining local patch trees, some fixes
> are sent 3 times by different people. How can we improve
> this insatisfying situation?
>
What are the unapplied patches? I have about 30 patches in my queue.
Even the oldest (which had comments so I'll probably drop from my queue)
are less than 2 weeks old. I don't have any unapplied patches from you
in my queue.
There are certain subsystems that do not have an active maintainer right
now. Really there is no solution for this without something stepping up
to active maintain those subsystems. That basically requires someone
devoting some time to maintaining a queue for that subsystem.
Regards,
Anthony Liguori
>
>
>
>
next prev parent reply other threads:[~2009-03-24 21:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 21:42 [Qemu-devel] [BUG] [PATCH] [STABLE] Fix monitor command (screendump) Stefan Weil
2009-03-24 21:47 ` Anthony Liguori [this message]
2009-03-24 22:31 ` Ryan Harper
2009-03-25 10:27 ` Stefano Stabellini
2009-03-28 17:29 ` Anthony Liguori
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=49C954E1.5030706@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=weil@mail.berlios.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).