From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu/target-mips helper.c translate.c (compiler error)
Date: Fri, 8 Dec 2006 00:00:43 +0000 [thread overview]
Message-ID: <200612080000.45469.paul@codesourcery.com> (raw)
In-Reply-To: <45789429.5080000@mail.berlios.de>
On Thursday 07 December 2006 22:22, Stefan Weil wrote:
> Paul, did you get my last mailing on this subject?
> (see http://lists.gnu.org/archive/html/qemu-devel/2006-05/msg00280.html)
My point exactly. Posting a link to a random website isn't sufficient,
especially when you say "my patches are still not ready for integration".
I think it's fair to say that everyone involved with qemu doesn't even have
time to do the things they are personally interested in. If you want to get
things integrated *you* have to put the effort in to get it submitted in a
form where that can happen.
Paul
next prev parent reply other threads:[~2006-12-08 0:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 16:22 [Qemu-devel] qemu/target-mips helper.c translate.c Thiemo Seufer
2006-12-07 18:44 ` [Qemu-devel] qemu/target-mips helper.c translate.c (compiler error) Stefan Weil
2006-12-07 18:48 ` Paul Brook
2006-12-07 19:54 ` Thiemo Seufer
2006-12-07 22:22 ` Stefan Weil
2006-12-08 0:00 ` Paul Brook [this message]
2006-12-07 20:11 ` Thiemo Seufer
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=200612080000.45469.paul@codesourcery.com \
--to=paul@codesourcery.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).