public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Arndt Schoenewald <abs-SA7OhAOe25xnNxvc45mVi0K323yFvGpRdefyYXQ/eNw@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Re: Administration Wishlist
Date: Sun, 25 Aug 2002 13:47:31 +0200	[thread overview]
Message-ID: <20020825114731.GD23319@schiggy.intern.quelltext.com> (raw)
In-Reply-To: <m2n0rf2e13.fsf-dTJq59+VGzkkCw8IV3R6h0EOCMrvLtNR@public.gmane.org>

On Thu, Aug 22, 2002 at 03:56:08PM +0200, Jan Rychter wrote:
> >>>>> "Arndt" == Arndt Schoenewald <abs-SA7OhAOe25xnNxvc45mVi0K323yFvGpRdefyYXQ/eNw@public.gmane.org>:
> 
>  Arndt> [...] I second his [Huw's] proposal that we would benefit from
>  Arndt> using a bug tracking system.
> 
> Indeed.
> 
> I have reported many problems with ACPI and I've been trying my best to
> do it precisely. Most of those were forgotten or lost somewhere. Some
> things eventually got fixed, some did not and are still broken for me.
> 
> I've given up on reporting bugs after the last time, when I tried to
> help with the issue of my fans not working. The issue apparently got
> lost.
> 
> I don't know much about ACPI, but in the software projects that I
> manage, properly tracked bug reports are very valuable and are not to be
> thrown away lightly.

Yes. We want people to report bugs, and we don't want bugs to be
reported more than once. The BTS helps to achieve both, and with
a low administrative overhead.

If it's okay for the "guys in charge" who are doing the programming
work (Andy, Pavel, David, Dominik et al?!), I suggest we just start
using the SourceForge bug tracker to a larger extent and then we'll
see what comes out of it.

Arndt


-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390

      parent reply	other threads:[~2002-08-25 11:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-22  0:20 Administration Wishlist Huw Hawkins
     [not found] ` <1029975625.6527.86.camel-v8X+xWjPZDc@public.gmane.org>
2002-08-22  1:01   ` Matthew Wilcox
     [not found]     ` <20020822020139.S29958-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>
2002-08-22 10:43       ` Arndt Schoenewald
     [not found]         ` <m2n0rf2e13.fsf@tnuctip.rychter.com>
     [not found]           ` <m2n0rf2e13.fsf-dTJq59+VGzkkCw8IV3R6h0EOCMrvLtNR@public.gmane.org>
2002-08-25 11:47             ` Arndt Schoenewald [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=20020825114731.GD23319@schiggy.intern.quelltext.com \
    --to=abs-sa7ohaoe25xnnxvc45mvi0k323yfvgprdefyyxq/enw@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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