qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@redhat.com>
To: Brian Jackson <iggy@theiggy.com>
Cc: Chris Wright <chrisw@redhat.com>,
	kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: KVM call agenda for May 18
Date: Tue, 18 May 2010 12:51:06 -0700	[thread overview]
Message-ID: <20100518195106.GL21120@x200.localdomain> (raw)
In-Reply-To: <201005181446.16487.iggy@theiggy.com>

* Brian Jackson (iggy@theiggy.com) wrote:
> On Tuesday 18 May 2010 08:52:36 Anthony Liguori wrote:
> > On 05/18/2010 01:59 AM, Brian Jackson wrote:
> > > On Monday 17 May 2010 22:23:46 Chris Wright wrote:
> > >> Please send in any agenda items you are interested in covering.
> > >> 
> > >> If we have a lack of agenda items I'll cancel the week's call.
> > > 
> > > Perceived long standing bugs that nobody seems to care about. There are a
> > > few, one of which is the>  1TB [1] bug that has existed for 4+ months.
> > 
> > s/care about/know about/g
> > 
> > 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.
> > 
> > > And others.
> > 
> > Bugs that affect qemu should be filed in launchpad.  Launchpad has nice
> > features like the able to mark bugs as affecting many users which help
> > raise visibility.  I can't speak for the source forge tracker, but I do
> > regular triage on launchpad for qemu bugs.
> 
> 
> I wonder how everyone would feel about closing the kvm tracker to new 
> submissions and move everything over to launchpad?

Yeah, this was suggested on the call today.  Anthony's sending out an
email proposal on better bug tracking

thanks,
-chris

  reply	other threads:[~2010-05-18 19:52 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 [this message]
2010-05-19  8:20     ` Christoph Hellwig
2010-05-19 19:47       ` Anthony Liguori
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=20100518195106.GL21120@x200.localdomain \
    --to=chrisw@redhat.com \
    --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).