All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: Andi Kleen <ak@suse.de>, Christoph Hellwig <hch@infradead.org>,
	Jeff Mahoney <jeffm@suse.com>,
	LKML <linux-kernel@vger.kernel.org>,
	kernel-bugzilla@luksan.cjb.net
Subject: Re: quality control
Date: Mon, 6 Feb 2006 14:44:16 +0100	[thread overview]
Message-ID: <20060206134415.GZ13598@suse.de> (raw)
In-Reply-To: <96DB44F5-85D3-4F78-8417-D5AB9303D696@mac.com>

On Mon, Feb 06 2006, Kyle Moffett wrote:
> On Feb 06, 2006, at 06:09, Andi Kleen wrote:
> >Kyle Moffett <mrmacman_g4@mac.com> writes:
> >>It's a GIT version of an RC patch for grief's sake!  You don't  
> >>seriously expect people to quadruple-check every trivial patch  
> >>that goes into Linus GIT tree before sending it, do you?
> >
> >No quadruple check, but every patch going to Linus should get at  
> >least some basic testing and it's definitely suppose to compile at  
> >least in one .config combination.
> 
> Well, yes, and it did.  The problem was that if you turned off ACLs,  
> it didn't work; only one or two variants of about 6 or 8 ways to  
> configure reiserfs stopped working.  Given that, I can't see how Hans  

Look, it's really simple: lets say I make a change that has to do with
PM, you do a quick compile test with and _without_ PM just to check you
didn't screw anything up with that change. You change reiserfs acl
stuff, you do a quick compile test with and without that configured.

It's a pretty standard procedure, and contrary to what you think, it
_is_ required before submitting a patch. No one is asking anyone to
check all possible configure options, but the interesting data set is
typically extremely easy to guess looking at a change.

-- 
Jens Axboe


  reply	other threads:[~2006-02-06 13:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <43E64791.8010302@namesys.com>
     [not found] ` <43E6521F.5020707@suse.com>
2006-02-06  3:15   ` quality control Hans Reiser
2006-02-06  3:39     ` Kyle Moffett
2006-02-06  9:09       ` Jens Axboe
2006-02-06  9:15       ` Martin Mares
2006-02-06 11:09       ` Andi Kleen
2006-02-06 13:31         ` Kyle Moffett
2006-02-06 13:44           ` Jens Axboe [this message]
2006-02-07 22:44             ` Andrew Morton
2006-02-08  8:45               ` Jens Axboe
2006-02-06 19:27         ` Olaf Hering

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=20060206134415.GZ13598@suse.de \
    --to=axboe@suse.de \
    --cc=ak@suse.de \
    --cc=hch@infradead.org \
    --cc=jeffm@suse.com \
    --cc=kernel-bugzilla@luksan.cjb.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrmacman_g4@mac.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.