From: David Woodfall <dave@unrealize.co.uk>
To: qemu-devel@nongnu.org
Subject: Re: Re: [Qemu-devel] qemu 0.11 and kqemu source question
Date: Mon, 21 Jun 2010 23:56:39 +0100 [thread overview]
Message-ID: <20100621225639.GB31589@Junius> (raw)
In-Reply-To: <4C1F7AAC.9010609@codemonkey.ws>
[-- Attachment #1: Type: text/plain, Size: 685 bytes --]
On (09:43 21/06/10), Anthony Liguori <anthony@codemonkey.ws> put forth the proposition:
> On 06/19/2010 08:58 PM, David Woodfall wrote:
>> Hi, I'm the maintainer for the kqemu and now qemu 0.11 slackbuilds at
>> slackbuilds.org and just wanted to find out if the old 0.11 sources
>> are likely to be continued to be hosted, or if it's likely they may be
>> removed at some point?
>
> Their location might change (from Savannah to qemu.org) but we'll
> continue to host archival releases for the foreseeable future.
Great, thanks.
David
>
> Regards,
>
> Anthony Liguori
>
>> Cheers
>>
>> David
>>
>
--
Don't look back, the lemmings are gaining on you.
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2010-06-21 22:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-20 1:58 [Qemu-devel] qemu 0.11 and kqemu source question David Woodfall
2010-06-21 14:43 ` Anthony Liguori
2010-06-21 22:56 ` David Woodfall [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=20100621225639.GB31589@Junius \
--to=dave@unrealize.co.uk \
--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).