qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Edgar E. Iglesias" <edgar.iglesias@axis.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Patches?
Date: Mon, 17 Mar 2008 17:48:54 +0100	[thread overview]
Message-ID: <20080317164854.GC8633@edgar.se.axis.com> (raw)
In-Reply-To: <47DE6FD6.4010206@mlbassoc.com>

On Mon, Mar 17, 2008 at 07:19:18AM -0600, Gary Thomas wrote:
> I've fixed a number of problems with the user mode code.
> Where's the best place to send/propose/discuss these?
> What's the preferred format?

Hello Gary,

Just send the patches to this list as unified diffs, preferably inlined to the email to ease reviewing. If the patch is large consider splitting it into several patches and emails.

Thanks
-- 
Edgar E. Iglesias
Axis Communications AB

      parent reply	other threads:[~2008-03-17 16:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-17 13:19 [Qemu-devel] Patches? Gary Thomas
     [not found] ` <200803171043.04220.computers57@hotmail.com>
2008-03-17 16:42   ` C.W. Betts
2008-03-17 17:36   ` Stuart Brady
2008-03-17 16:48 ` Edgar E. Iglesias [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=20080317164854.GC8633@edgar.se.axis.com \
    --to=edgar.iglesias@axis.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).