qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Christoph Hellwig <hch@infradead.org>
Cc: Brian Jackson <iggy@theiggy.com>,
	Chris Wright <chrisw@redhat.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: KVM call agenda for May 18
Date: Wed, 19 May 2010 14:47:29 -0500	[thread overview]
Message-ID: <4BF44051.4090403@codemonkey.ws> (raw)
In-Reply-To: <20100519082016.GA2344@infradead.org>

On 05/19/2010 03:20 AM, Christoph Hellwig wrote:
> On Tue, May 18, 2010 at 08:52:36AM -0500, Anthony Liguori wrote:
>    
>> This should be filed in launchpad as a qemu bug and it should be tested
>> against the latest git.  This bug sounds like we're using an int to
>> represent sector offset somewhere but there's not enough info in the bug
>> report to figure out for sure.  I just audited the virtio-blk ->  raw ->
>> aio=threads path and I don't see an obvious place that we're getting it
>> wrong.
>>      
> FYI: I'm going to ignore everything that's in launchpad - even more than
> in the stupid SF bugtracker.  While the SF one is almost unsuable
> launchpad is entirely unsuable.  If you don't have an account with the
> evil spacement empire you can't even check the email addresses of the
> reporters, so any communication with them is entirely impossible.
>    

All bug traffic will now come to the list and you can just respond 
directly to that.  The mails include the submitters contact information.

Regards,

Anthony Liguori

> It's time we get a proper bugzilla.qemu.org for both qemu and qemu-kvm
> that can be used sanely.  If you ask nicely you might even get a virtual
> instance of bugzilla.kernel.org which works quite nicely.
>
>    

  reply	other threads:[~2010-05-19 19:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-18  3:23 [Qemu-devel] KVM call agenda for May 18 Chris Wright
2010-05-18  6:59 ` [Qemu-devel] " Brian Jackson
2010-05-18 13:52   ` Anthony Liguori
2010-05-18 19:46     ` Brian Jackson
2010-05-18 19:51       ` Chris Wright
2010-05-19  8:20     ` Christoph Hellwig
2010-05-19 19:47       ` Anthony Liguori [this message]
2010-05-25  9:51       ` Avi Kivity
2010-05-18 13:53 ` Anthony Liguori
2010-05-18 14:09   ` Daniel P. Berrange
2010-05-18 14:34     ` Anthony Liguori
2010-05-18 14:55       ` Daniel P. Berrange
2010-05-18 15:26         ` Anthony Liguori
2010-05-18 15:44         ` Markus Armbruster
2010-05-18 15:48           ` Markus Armbruster
2010-05-18 16:00         ` Luiz Capitulino
2010-05-18 16:16           ` Daniel P. Berrange
2010-05-18 16:25             ` Anthony Liguori
2010-05-18 17:46             ` Luiz Capitulino
2010-05-18 17:31       ` Avi Kivity
2010-05-18 21:50         ` Anthony Liguori

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=4BF44051.4090403@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=chrisw@redhat.com \
    --cc=hch@infradead.org \
    --cc=iggy@theiggy.com \
    --cc=kvm@vger.kernel.org \
    --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).