All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kip Macy <kip.macy@gmail.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Fw: Bug tracking system
Date: Wed, 13 Apr 2005 10:47:09 -0700	[thread overview]
Message-ID: <b1fa2917050413104768b56f5f@mail.gmail.com> (raw)
In-Reply-To: <OF0D0F8113.52FD2D19-ON86256FE2.0060CBC7-86256FE2.00611266@us.ibm.com>

There was some talk of using TRAC. The only argument given for not
having one yet is waiting until -unstable is stable enough that the
reported bugs are actual bugs and not artifacts of incompletely
implemented features.

I understand the reasoning, but it would be nice to have a better
mechanism for determining if a problem one is seeing is new or not.

       -Kip


On 4/13/05, Stephanie Glass <sglass@us.ibm.com> wrote:
> 
> 
> >Paul Larson wrote:
> >
> >There was some discussion some time ago about a bug tracking system for
> >Xen.  Is there any plan on when that will be available?
> 
> I like to vote for the bug tracking system to come sooner versus later.  I
> have notice that
> there are several bugs that keep coming back up on the mailing list and if
> we had a bug track
> tracking system, we would be able to put it out once.  Then as people have
> time, they could
> pick different bugs and supply fixes for them by assinging the bug to
> themselves.
> 
> Stephanie Glass
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>

      reply	other threads:[~2005-04-13 17:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-13 17:40 Fw: Bug tracking system Stephanie Glass
2005-04-13 17:47 ` Kip Macy [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=b1fa2917050413104768b56f5f@mail.gmail.com \
    --to=kip.macy@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.