From: "Mulyadi Santosa" <mulyadi.santosa@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu bug track
Date: Fri, 11 Jan 2008 14:40:22 +0700 [thread overview]
Message-ID: <f284c33d0801102340h58038924j14f7c9522c0d7df@mail.gmail.com> (raw)
In-Reply-To: <9c10c9f0801100928s3d88cf51r4c6b5c8abb1b96a9@mail.gmail.com>
Hi..
On Jan 11, 2008 12:28 AM, Lauro Ramos Venancio <lauro.venancio@gmail.com> wrote:
> I've set up an experimental bug track for Qemu stable branch. If the
> community wants it can be used for qemu head too.
>
> If the community agrees, I will do the configuration to send an email
> to qemu mailing list when a bug is opened.
>
> Let me know if someone (especially the developers that have write
> permission on cvs) wants permission on bug track administration.
>
> The bug track:
> https://launchpad.net/qemu
Just wanna say, I think it's really a good idea. Keep up the good work!
regards,
Mulyadi.
prev parent reply other threads:[~2008-01-11 7:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 17:28 [Qemu-devel] Qemu bug track Lauro Ramos Venancio
2008-01-11 7:40 ` Mulyadi Santosa [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=f284c33d0801102340h58038924j14f7c9522c0d7df@mail.gmail.com \
--to=mulyadi.santosa@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).