qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Jim C. Brown" <jma5@umd.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Norton Ghost crashes with page fault for me too.
Date: Tue, 14 Jun 2005 16:27:12 -0400	[thread overview]
Message-ID: <20050614202712.GA32761@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <002c01c57104$877421b0$334d21d1@organiza3bfb0e>

On Tue, Jun 14, 2005 at 12:14:05PM -0500, jeebs@yango.us wrote:
> Not all of us are developers.
> 
> The best that many can do is test qemu and report problems when they are 
> found.
> 
> Some of us do a bit more, by deliberately testing qemu with lots of 
> software, looking for bugs.  And reporting bugs when they are found.

If you really want a bug to be fixed badly, and you have no idea of how to fix
it, what you need to do is contact the developer of that code and let that
person know about the bug.

E.g. I'm the developer of the gtk2 interface for qemu, and I have no idea about
what bugs it may have as no one has reported any to me. In fact, I have no idea
if anyone is even using it because I get no direct feedback. This is especially
true for using the gtk2 interface under Windows, because I am unable to test
the code there. If someone who could test it did, and told me about the bug,
I'd fix it right away.

The only problem with this approach is that the section of code you are interested
in having fixed may not have an active developer (person left a while ago or
it was a section written by Fabrice himself that he doesn't have time to go
over anymore). In that case, there isn't much you can do. Documenting bugs is
still good because a) we can let other users know its a known bug and b) when
a new maintainer for that section of code comes along, they'll be able to get
started on the fixes right away. But this is only satisfactory if you are a very
patient person.

> 
> But that's no excuse for bug reports to just vanish into the void.  Without 
> an awknowledgement or somebody writting it down as a bug in qemu that needs 
> to get fixed eventually.
> 

No one looks at the Savanah bug tracker because its never been used. If you were
to say submit every unfixed bug you found there, just maybe those of us who
bother to look every once in a while will see it and fix it.

Do this often enough and others will use it, etc... the qemu user forum and
the qemu irc channel developed in much the same way.

-- 
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.

  parent reply	other threads:[~2005-06-14 20:28 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-13 17:49 [Qemu-devel] Norton Ghost crashes with page fault for me too Jeff Wiegley
2005-06-14  2:37 ` jeebs
2005-06-14 13:43   ` Ishwar Rattan
2005-06-14 16:39     ` Henrik Nordstrom
2005-06-14 17:14       ` jeebs
2005-06-14 17:40         ` Henrik Nordstrom
2005-06-14 18:51           ` jeebs
2005-06-15  4:08             ` Herbert Poetzl
2005-06-14 20:27         ` Jim C. Brown [this message]
2005-06-14 20:54           ` [Qemu-devel] " Ronald
2005-06-14 21:15           ` [Qemu-devel] " jeebs
2005-06-14 22:18             ` Jim C. Brown
2005-06-14 23:02               ` jeebs
2005-06-15  9:23                 ` Jernej Simončič
2005-06-15 17:30                   ` jeebs
2005-06-15 13:36                 ` Henrik Nordstrom
2005-06-14 21:46           ` [Qemu-devel] " Heike C. Zimmerer
2005-06-14 22:43             ` Jim C. Brown
2005-06-15 17:28               ` jeebs
2005-06-15 18:54                 ` Jim C. Brown
2005-06-15 18:11               ` Heike C. Zimmerer
2005-06-14 16:30   ` [Qemu-devel] " Henrik Nordstrom
2005-06-14 17:11     ` jeebs
2005-06-15 13:20       ` Henrik Nordstrom
2005-06-14 13:54 ` Elefterios Stamatogiannakis
2005-06-14 15:45   ` Andreas Bollhalder

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=20050614202712.GA32761@jbrown.mylinuxbox.org \
    --to=jma5@umd.edu \
    --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).