From: Olaf Hering <olh@suse.de>
To: Andi Kleen <ak@suse.de>
Cc: Kyle Moffett <mrmacman_g4@mac.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 20:27:21 +0100 [thread overview]
Message-ID: <20060206192721.GA8600@suse.de> (raw)
In-Reply-To: <p73hd7clp5k.fsf@verdi.suse.de>
On Mon, Feb 06, 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.
Right. We have now git-bisect, and it helped me to nail down a few bugs.
Just now I track down some scsi or whatever breakage in -rc1. And guess
what, not a single compile error so far, with a full featured config!
So you guys better send tested patches, via akpm, to keep Linus tree in
a reasonable shape.
--
short story of a lazy sysadmin:
alias appserv=wotan
prev parent reply other threads:[~2006-02-06 19:27 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
2006-02-07 22:44 ` Andrew Morton
2006-02-08 8:45 ` Jens Axboe
2006-02-06 19:27 ` Olaf Hering [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=20060206192721.GA8600@suse.de \
--to=olh@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.