public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Mark Gross <mgross@linux.intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why is 2.6.12.2 less stable on my laptop than 2.6.10?
Date: Fri, 15 Jul 2005 10:45:05 +0200	[thread overview]
Message-ID: <20050715084505.GD1772@elf.ucw.cz> (raw)
In-Reply-To: <200507140912.22532.mgross@linux.intel.com>

Hi!

> Why can't I expect SWSusp work better and more reliable from release to 
> release?  

Patches welcome. Or employ someone to do swsusp development for you.

> Some possible things that could help:
> 
> *Addopt a no-regressions-allowed policy and everthing stops until any 
> identified regressions (in performance, functionally or stability) is fixed 
> or the changes are all rolled back.  This works really well if in addition 
> organized pre-flight testing is done before calling a new version number.  
> You simply cannot rely on ad-hock regression testing and reporting.  Its got 
> too much latency.

This would also mean "no development at all".

> * assign validation folks that the developer need to appease before changes 
> are allowed to be accepted into the tree. 

So... get me someone to test swsusp in each -rc and -mm
release... that would help. If you can't provide the manpower, why are
you whining?

									Pavel
-- 
teflon -- maybe it is a trademark, but it should not be.

  parent reply	other threads:[~2005-07-16 13:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-14 16:12 Why is 2.6.12.2 less stable on my laptop than 2.6.10? Mark Gross
2005-07-14 23:55 ` Andrew Morton
2005-07-15  8:45 ` Pavel Machek [this message]
     [not found] <200507140912.22532.mgross@linux.intel.com.suse.lists.linux.kernel>
2005-07-15  0:38 ` Andi Kleen
2005-07-15  1:45   ` Jesper Juhl
2005-07-15  2:02     ` Chris Friesen
2005-07-15  2:06       ` Jesper Juhl
2005-07-15  2:09         ` Andi Kleen
2005-07-15 21:33           ` Mark Gross
2005-07-15  2:16         ` Dave Airlie
2005-07-15 21:39           ` Mark Gross
2005-07-15  2:09     ` Dave Jones
2005-07-15 21:47       ` Mark Gross
2005-07-15 22:19         ` Dave Jones
2005-07-15 22:25         ` David Lang
2005-07-15 23:14         ` Rik van Riel
2005-07-18 21:14           ` Mark Gross
2005-07-19 10:12             ` Paolo Ciarrocchi
2005-07-15  2:09   ` Parag Warudkar
2005-07-15  2:14     ` Andi Kleen
2005-07-15 13:32     ` Alan Cox

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=20050715084505.GD1772@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgross@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox