linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Adrian Bunk <bunk@kernel.org>,
	Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Natalie Protasevich <protasnb@gmail.com>
Subject: Re: kernel bugzilla is FPOS (was: Re: "buggy cmd640" message followed by soft lockup)
Date: Sun, 25 Nov 2007 20:08:00 +0000	[thread overview]
Message-ID: <20071125200800.GA9808@gallifrey> (raw)
In-Reply-To: <200711252107.23926.rjw@sisk.pl>

* Rafael J. Wysocki (rjw@sisk.pl) wrote:

<snip>
 (many levels of quote)

> > > > * Bugs that sit in NEEDINFO state for more than i.e. one month should be
> > > >   automatically closed.
> > > 
> > > I agree that we probably should do something like this.
> >  
> > Not automatically.
> 
> OK, say "as a rule".

The only thing I would say is that a reporter can be in a situation
after a while where they no longer have access to the original
machine; if the bug was originally believed to be real and triaged
then it seems to make sense to differentiate that from a bug that is
just closed, just so people can know there is an issue with
a configuration.

Dave

-- 
 -----Open up your eyes, open up your mind, open up your code -------   
/ Dr. David Alan Gilbert    | Running GNU/Linux on Alpha,68K| Happy  \ 
\ gro.gilbert @ treblig.org | MIPS,x86,ARM,SPARC,PPC & HPPA | In Hex /
 \ _________________________|_____ http://www.treblig.org   |_______/

  reply	other threads:[~2007-11-25 20:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-22 19:07 "buggy cmd640" message followed by soft lockup Frans Pop
     [not found] ` <200711241904.13132.bzolnier@gmail.com>
2007-11-24 19:07   ` Rafael J. Wysocki
2007-11-25  0:26     ` kernel bugzilla is FPOS (was: Re: "buggy cmd640" message followed by soft lockup) Bartlomiej Zolnierkiewicz
2007-11-25 13:11       ` Rafael J. Wysocki
2007-11-25 13:49         ` Adrian Bunk
2007-11-25 20:07           ` Rafael J. Wysocki
2007-11-25 20:08             ` Dr. David Alan Gilbert [this message]
2007-11-25 20:32             ` Adrian Bunk
2007-11-25 21:28               ` Rafael J. Wysocki
2007-11-25 21:36                 ` Adrian Bunk
2007-11-25 22:38                   ` Rafael J. Wysocki
2007-11-25 22:40                     ` Adrian Bunk
2007-11-25 23:28                       ` Rafael J. Wysocki
2007-11-25 23:34                         ` Adrian Bunk
2007-11-26  0:30                           ` Rafael J. Wysocki
2007-11-26 21:45                             ` Adrian Bunk
2007-11-26 22:57                               ` Rafael J. Wysocki
2007-11-25 22:55                     ` Rafael J. Wysocki
2007-11-25 14:08         ` Bartlomiej Zolnierkiewicz
2007-11-25 20:25           ` Rafael J. Wysocki
     [not found]   ` <200711242038.06677.elendil@planet.nl>
2007-11-24 20:12     ` "buggy cmd640" message followed by soft lockup Rafael J. Wysocki
     [not found]     ` <200711250013.51279.bzolnier@gmail.com>
2007-11-26  1:32       ` Frans Pop

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=20071125200800.GA9808@gallifrey \
    --to=linux@treblig.org \
    --cc=akpm@linux-foundation.org \
    --cc=bunk@kernel.org \
    --cc=bzolnier@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=protasnb@gmail.com \
    --cc=rjw@sisk.pl \
    /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).