public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>,
	dtor_core@ameritech.net, Chris Wright <chrisw@osdl.org>,
	jgarzik@pobox.com, olof@austin.ibm.com, paulus@samba.org,
	rene@exactcode.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] trivial fix for 2.6.11 raid6 compilation on ppc w/ Altivec
Date: Fri, 4 Mar 2005 10:41:24 -0800	[thread overview]
Message-ID: <20050304184124.GC29857@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0503041031110.25732@ppc970.osdl.org>

On Fri, Mar 04, 2005 at 10:38:10AM -0800, Linus Torvalds wrote:
> 
> 
> On Fri, 4 Mar 2005, Greg KH wrote:
> > 
> > Ok, based on consensus, I've applied this one too.
> 
> Btw, I don't think your process works. You never really gave people the
> time to object. So for that reason you applied the first trivial raid6
> thing, and it turned out to be wrong.

I agree.

> I think the patches need to have a rule like "they live outside the sucker 
> tree for at least two days". And during that time, anybody can vote them 
> down (which would move them to "unapplied" status, at which point somebody 
> else might decide that for _their_ tree it's still the right thing to do).
> 
> And if at the end of two days, they still haven't gotten enough "yes"  
> votes, they'd go into "limbo" status, with one extra grace-period (ie a
> reminder on whatever list about a patch that is dying). And if it can't 
> get enough "yeah, sure" votes even after that, it goes into the same 
> "unapplied" list.
> 
> In other words, I think this really does want some automation. It
> shouldn't be fully automated (at the very least, somebody needs to
> actually check that things patch and fix up the changeset comments etc),
> but the _rules_ should be automated. Otherwise they'll always be broken
> because of "_this_ time it's obvious", which is against the point.

Ok, Chris and I are going to sit down and work this all out on Tuesday.
I'll hold off on applying or releasing anything else until we fully
describe the process, and set up the infrastructure.

I'll slow down now :)

thanks,

greg k-h

  reply	other threads:[~2005-03-04 18:59 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-03 18:05 [PATCH] trivial fix for 2.6.11 raid6 compilation on ppc w/ Altivec Rene Rebe
2005-03-03 18:26 ` Jeff Garzik
2005-03-03 18:48   ` Greg KH
2005-03-03 18:59     ` Rene Rebe
2005-03-03 19:18   ` Greg KH
2005-03-03 19:48     ` Jeff Garzik
2005-03-03 20:07       ` Chris Wright
2005-03-03 20:32         ` Greg KH
2005-03-03 20:57           ` Jeff Garzik
2005-03-04 12:10             ` Francois Romieu
2005-03-03 22:30   ` Paul Mackerras
2005-03-03 22:45     ` Greg KH
2005-03-03 23:05       ` Dave Jones
2005-03-03 22:55     ` Olof Johansson
2005-03-03 23:14       ` Greg KH
2005-03-04  1:59       ` Andrew Morton
2005-03-04  2:24         ` Olof Johansson
2005-03-04  5:54           ` Chris Wright
2005-03-04  6:06             ` Jeff Garzik
2005-03-04  6:17               ` Andrew Morton
2005-03-04  6:33                 ` Jeff Garzik
2005-03-04  6:06             ` Andrew Morton
2005-03-04  6:12               ` Jeff Garzik
2005-03-04  6:20                 ` Andrew Morton
2005-03-04  6:20                 ` Chris Wright
2005-03-04  6:23                   ` Andrew Morton
2005-03-04  6:47                     ` Chris Wright
2005-03-04  6:54                       ` Andrew Morton
2005-03-04  7:04                         ` Chris Wright
2005-03-04  7:05                       ` Jeff Garzik
2005-03-04  7:12                         ` Andrew Morton
2005-03-04  7:14                           ` Jeff Garzik
2005-03-04 16:27                     ` Greg KH
2005-03-04 18:38                       ` Linus Torvalds
2005-03-04 18:41                         ` Greg KH [this message]
2005-03-06 23:06                       ` Alan Cox
2005-03-07 18:03                         ` 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=20050304184124.GC29857@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=chrisw@osdl.org \
    --cc=dtor_core@ameritech.net \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@austin.ibm.com \
    --cc=paulus@samba.org \
    --cc=rene@exactcode.de \
    --cc=torvalds@osdl.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