qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Stefan Weil <weil@mail.berlios.de>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] win32: Add missing function setenv
Date: Fri, 02 Jul 2010 10:40:47 +0200	[thread overview]
Message-ID: <4C2DA60F.5040904@redhat.com> (raw)
In-Reply-To: <4C2CD625.3040300@mail.berlios.de>

On 07/01/10 19:53, Stefan Weil wrote:
> Two patches are needed anyway.
> 
> For reasons of economy, I won't send a new patch.
> Feel free do send one which meets your criteria.
> 
> Regards,
> Stefan
> 

Well if you are not interested in working the way the community works,
please don't expect us to fix your bugs either.

Jes

      reply	other threads:[~2010-07-02  8:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-01 10:47 [Qemu-devel] [PATCH] win32: Add missing function setenv Stefan Weil
2010-07-01 11:50 ` Jes Sorensen
2010-07-01 13:22   ` Stefan Weil
2010-07-01 13:24     ` Jes Sorensen
2010-07-01 15:51       ` Stefan Weil
2010-07-01 15:53         ` Jes Sorensen
2010-07-01 17:53           ` Stefan Weil
2010-07-02  8:40             ` Jes Sorensen [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=4C2DA60F.5040904@redhat.com \
    --to=jes.sorensen@redhat.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).