public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: Hans Reiser <reiser@namesys.com>,
	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 10:09:16 +0100	[thread overview]
Message-ID: <20060206090915.GJ13598@suse.de> (raw)
In-Reply-To: <BAFD888C-7E6B-49B1-A394-901D24CFBCBF@mac.com>

On Sun, Feb 05 2006, Kyle Moffett wrote:
> On Feb 05, 2006, at 22:15, Hans Reiser wrote:
> >Jeff Mahoney wrote:
> >>Hans Reiser wrote:
> >>>http://bugzilla.kernel.org/show_bug.cgi?id=6016
> >>>          Summary: reiserfs doesn't build with  
> >>>REISERFS_FS_POSIX_ACL=n
> >>>   Kernel Version: v2.6.16-rc2-g5b7b644
> >>
> >>This was a patch from hch, not me. There's already a patch in -mm to
> >>fix it.
> >
> >Please consider adhering to a quality control process.
> 
> 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?  The whole point  
> of the RC is to indicate that only smaller patches should be applied  
> (and this one was for the most part) so that we can do some kind of  
> global-kernel QC.

Eh, but you are expected to do that. If everybody sent in half-assed not
tested patches "just because" it's a pre-rc, things would look bad.
Compile testing is the least time consuming and easiest thing to to
test, so you should at least do that. If nobody did that, no one would
get snapshots tested because they would never compile for anyone.

For developers it's equally annoying. I typically update my tree every
morning and run with that for the various stuff I'm working on, and it
is really annoying to have to spent time on hunting down and fixing
compile errors.

This mail is about the mentality displayed, not the specific change that
spawned it.

-- 
Jens Axboe


  reply	other threads:[~2006-02-06  9:07 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 [this message]
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
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=20060206090915.GJ13598@suse.de \
    --to=axboe@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 \
    --cc=reiser@namesys.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