All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-kernel@vger.kernel.org, Chris Wright <chrisw@osdl.org>,
	torvalds@osdl.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [RFC] -stable, how it's going to work.
Date: Thu, 10 Mar 2005 08:43:12 -0800	[thread overview]
Message-ID: <20050310164312.GC16126@kroah.com> (raw)
In-Reply-To: <16944.6867.858907.990990@cse.unsw.edu.au>

On Thu, Mar 10, 2005 at 09:00:51PM +1100, Neil Brown wrote:
> On Tuesday March 8, greg@kroah.com wrote:
> > So here's a first cut at how this 2.6 -stable release process is going
> > to work that Chris and I have come up with.  Does anyone have any
> > problems/issues/questions with this?
> 
> One rule that I thought would make sense, but that I don't see listed
> is:
> 
>  - must fix a regression

That, and a zillion other specific wordings that people suggested fall
under the:
	or some "oh, that's not good" issue
rule.

I didn't feel like being all lawyer-like and explicitly spelling out all
of the different kinds of bugs that we would be accepting patches for :)

So yes, I don't have a problem with patches to fix regressions.

thanks,

greg k-h

  parent reply	other threads:[~2005-03-10 16:50 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09  7:28 [RFC] -stable, how it's going to work Greg KH
2005-03-09  9:56 ` Andi Kleen
2005-03-09 10:10   ` Arjan van de Ven
2005-03-09 10:17     ` Russell King
2005-03-09 10:24       ` Arjan van de Ven
2005-03-09 10:32         ` Russell King
2005-03-09 10:28       ` Andi Kleen
2005-03-09 14:20   ` Marcelo Tosatti
2005-03-09 18:00   ` Alan Cox
2005-03-09 18:29     ` Greg KH
2005-03-09 18:29     ` Chris Wright
2005-03-09 19:30     ` Andi Kleen
2005-03-09 18:28   ` Chris Wright
2005-03-09 19:44     ` Andi Kleen
2005-03-09 20:16       ` Chris Wright
2005-03-09 22:49       ` Russell King
2005-03-09 18:34   ` Greg KH
2005-03-09 19:39     ` Andi Kleen
2005-03-09 20:03       ` Greg KH
2005-03-09 20:25   ` Bill Davidsen
2005-03-10 10:00 ` Neil Brown
2005-03-10 10:17   ` Arjan van de Ven
2005-03-11  1:49     ` Neil Brown
2005-03-11  4:58       ` Chris Friesen
2005-03-11  7:07         ` Andi Kleen
2005-03-10 16:43   ` Greg KH [this message]
2005-03-10 17:27     ` Lee Revell
2005-03-10 17:31       ` Greg KH
2005-03-10 18:25         ` Lee Revell
2005-03-11 10:13           ` Pavel Machek
2005-03-10 17:43       ` Chris Wright
2005-03-10 17:51         ` Lee Revell
2005-03-10 17:44       ` Linus Torvalds
2005-03-11  0:10     ` Neil Brown
2005-03-11  2:43       ` J. Bruce Fields

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=20050310164312.GC16126@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=chrisw@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    --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 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.