From: "Lauro Ramos Venancio" <lauro.venancio@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu 0.9.1 stable branch
Date: Thu, 10 Jan 2008 16:05:18 -0300 [thread overview]
Message-ID: <9c10c9f0801101105q3cada8c3wb1a2196eac56ede6@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.1.00.0801101700390.31053@racer.site>
> So, Lauros, seems like all the commits since 0.9.1 (including the two new
> ones, "Fix typo which broke MIPS32R2 64-bit FPU support" and "qemu
> manpage: describe arguments of usbdevice option, by Aurelien Jarno") are
> candidates for the stable branch...
applied.
Lauro
prev parent reply other threads:[~2008-01-10 19:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 19:03 [Qemu-devel] Qemu 0.9.1 stable branch Lauro Ramos Venancio
2008-01-09 19:08 ` Jonathan Kalbfeld
2008-01-09 19:11 ` Johannes Schindelin
2008-01-09 19:11 ` Alexey Eremenko
2008-01-09 19:15 ` Johannes Schindelin
2008-01-10 15:50 ` Thiemo Seufer
2008-01-10 17:02 ` Johannes Schindelin
2008-01-10 19:05 ` Lauro Ramos Venancio [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=9c10c9f0801101105q3cada8c3wb1a2196eac56ede6@mail.gmail.com \
--to=lauro.venancio@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--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).