public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Release Policy
Date: 26 Nov 2001 17:32:18 -0800	[thread overview]
Message-ID: <9tuqf2$eri$1@cesium.transmeta.com> (raw)
In-Reply-To: <4.3.2.7.2.20011126113409.00bfaa70@mail.osagesoftware.com> <Pine.LNX.4.21.0111261328450.13681-100000@freak.distro.conectiva> <3C02E682.4CDC6858@zip.com.au> <20011126.171301.50592818.davem@redhat.com>

Followup to:  <20011126.171301.50592818.davem@redhat.com>
By author:    "David S. Miller" <davem@redhat.com>
In newsgroup: linux.dev.kernel
>
>    From: Andrew Morton <akpm@zip.com.au>
>    Date: Mon, 26 Nov 2001 17:04:02 -0800
>    
>    Marcelo, if someone sends you a patch which has not been thoroughly
>    reviewed on the appropriate mailing list, I would urge you to
>    peremptorily shitcan it.  There is no reason why you alone should
>    be responsible for reviewing kernel changes.
> 
> Are you suggesting that, for example, I should send every Sparc change
> to this list?
> 

appropriate != this.

> I bet a lot of what he is seeing are driver and arch updates.
> 
> Such updates really only need to go through his "stupid filter"
> when it is coming from the maintainer, but it does add up and
> take up time.

Obviously.  If it's for a maintained subsystem:

a) if it's from the subsystem maintainer, sanity-check it.
b) if it's not, dump it or reject with the appropriate notice.

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt	<amsp@zytor.com>

  reply	other threads:[~2001-11-27  1:32 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.21.0111261003070.13400-100000@freak.distro.cone ctiva>
2001-11-26 16:38 ` Release Policy [was: Linux 2.4.16 ] David Relson
2001-11-26 15:33   ` Marcelo Tosatti
2001-11-26 17:14     ` David Relson
2001-11-26 21:15       ` Bill Davidsen
2001-11-26 17:22     ` Chris Meadors
2001-11-26 15:54       ` Marcelo Tosatti
2001-11-26 17:41         ` David Rees
2001-11-26 18:12         ` H. Peter Anvin
2001-11-26 18:29           ` David Weinehall
2001-11-26 18:31             ` H. Peter Anvin
2001-11-26 17:25               ` Marcelo Tosatti
2001-11-26 18:49                 ` H. Peter Anvin
2001-11-26 19:00                 ` François Cami
2001-11-26 19:06                 ` Jonathan Lundell
2001-11-26 19:28                   ` Flavio Stanchina
2001-11-26 19:43                     ` Jonathan Lundell
2001-11-26 19:36                 ` David Weinehall
2001-11-26 20:39                 ` junio
2001-11-26 20:55                   ` David Weinehall
2001-11-26 20:59                     ` H. Peter Anvin
2001-11-26 21:18               ` Gregory Maxwell
2001-11-27  8:02                 ` Svein Erik Brostigen
2001-11-27  8:28                   ` Allan Sandfeld
2001-11-27  9:08                     ` Svein Erik Brostigen
2001-11-27 10:07                 ` Alex Bligh - linux-kernel
2001-11-27 14:43                 ` Sven Vermeulen
2001-11-27 15:01                   ` Ian Molton
2001-11-27 15:42                   ` John Alvord
2001-11-27 16:03                   ` Michel Angelo da Silva Pereira
2001-11-26 18:48       ` Bjoern A. Zeeb
2001-11-26 23:15         ` J.A. Magallon
2001-11-27  1:04     ` Andrew Morton
2001-11-27  1:13       ` Release Policy David S. Miller
2001-11-27  1:32         ` H. Peter Anvin [this message]
2001-11-27  7:39           ` Anuradha Ratnaweera
2001-11-27  7:40             ` H. Peter Anvin
2001-11-27  7:53               ` Anuradha Ratnaweera
2001-11-27 10:08             ` Harald Arnesen
2001-11-27 10:29               ` Keith Owens
2001-11-27 19:45                 ` Mike Fedyk
2001-12-05 14:27         ` Jes Sorensen
     [not found] <fa.c4d6r2v.j10a8j@ifi.uio.no>
     [not found] ` <fa.h6dlovv.r28grf@ifi.uio.no>
2001-11-27 10:25   ` Giacomo Catenazzi

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='9tuqf2$eri$1@cesium.transmeta.com' \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    /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