From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: "Kirill A. Shutemov" <k.shutemov@gmail.com>
Subject: Re: [Qemu-devel] Bugs. Patches. Feedback.
Date: Sun, 4 Mar 2007 13:31:55 +0000 [thread overview]
Message-ID: <200703041331.55895.paul@codesourcery.com> (raw)
In-Reply-To: <20070304115219.GC12454@localhost.localdomain>
On Sunday 04 March 2007 11:52, Kirill A. Shutemov wrote:
> I want to help qemu project, but some patches which I post to the mail
> list have ignored. I guess that a open source project should have faster
> feedback.
Giving some description of the patches might help. Patches with no explanation
or justification generally go straight to the bottom of my queue.
> [PATCH] syscall uselib
This one is almost certainly wrong. I very much doubt the host kernel is going
to do anything useful with target binaries. This is a seriously crufty
syscall anyway.
Paul
prev parent reply other threads:[~2007-03-04 13:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-04 11:52 [Qemu-devel] Bugs. Patches. Feedback Kirill A. Shutemov
2007-03-04 13:31 ` Paul Brook [this message]
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=200703041331.55895.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=k.shutemov@gmail.com \
--cc=qemu-devel@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).