From: Stuart Brady <sdbrady@ntlworld.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] cocoa.m issues fixed
Date: Mon, 22 Jun 2009 19:47:44 +0100 [thread overview]
Message-ID: <20090622184744.GA3626@miranda.arrow> (raw)
In-Reply-To: <f43fc5580906221035i1203c8b0h98df38888b43e050@mail.gmail.com>
On Mon, Jun 22, 2009 at 08:35:29PM +0300, Blue Swirl wrote:
> On 6/22/09, Stuart Brady <sdbrady@ntlworld.com> wrote:
> > Why are the birds being brought back to life, anyway? I thouht they idea
> > was to kill two birds with one stone?
>
> Yes, but since the maintainer reversed the patch, the birds and the
> kitten were magically resurrected.
So you mean, bring the kitten and the birds back to life, and then kill
the birds again? *Mind boggles*. Ah. Perhaps that was the point. :-)
(I see now that the birds would have to be revived, by necessity rather
than by choice, unless the correct stones are found in a timely manner.)
> > Consider the lily?! He's having a go at the flowers, now! ;-)
>
> ENOPARSE
Just a reference to Monty Python's Life of Brian, is all. :-)
> > * Improves the likelihood that maintainers will consider your patch
> > to be reviewable, and then actually review it and apply it, if those
> > maintainers lack the time to review all patches that are submitted.
>
> +1 for this one.
Ah, I thought that one might prove popular. :-)
Cheers,
--
Stuart Brady
prev parent reply other threads:[~2009-06-22 18:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-21 1:19 [Qemu-devel] [PATCH] cocoa.m issues fixed G 3
2009-06-21 10:10 ` Andreas Färber
2009-06-21 14:06 ` G 3
2009-06-21 15:23 ` Avi Kivity
2009-06-21 18:07 ` Blue Swirl
2009-06-21 18:16 ` Avi Kivity
2009-06-22 17:05 ` Stuart Brady
2009-06-22 17:35 ` Blue Swirl
2009-06-22 18:47 ` Stuart Brady [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=20090622184744.GA3626@miranda.arrow \
--to=sdbrady@ntlworld.com \
--cc=blauwirbel@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).