public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Kegel <dkegel@ixiacom.com>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.17
Date: Fri, 21 Dec 2001 13:59:11 -0800	[thread overview]
Message-ID: <3C23B0AF.311FE86A@ixiacom.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0112211744080.7492-100000@freak.distro.conectiva>

Marcelo Tosatti wrote:
> 
Marcelo wrote:
> > Um, what happened to the idea of 'no changes between the last
> > release candidate and final'?
> 
> I haven't said that, did I?
> 
> I said I would make -rc kernels which would not add any new _feature_.

Sorry; I must have misunderstood.  But I think lwn.net 
misunderstood, too; http://lwn.net/2001/1213/kernel.php3
says "Marcelo's stated plan is to have the final release be the same 
as the last release candidate; the hope is to be done with surprises 
caused by last-minute patches."

I guess I and lwn.net were projecting our desires onto Marcello's statements?

- Dan

  reply	other threads:[~2001-12-21 22:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-21 20:16 Linux 2.4.17 Dan Kegel
2001-12-21 19:44 ` Marcelo Tosatti
2001-12-21 21:59   ` Dan Kegel [this message]
2001-12-21 22:11     ` Rik van Riel
2001-12-21 23:10   ` Oliver Xymoron
2001-12-22  0:34   ` David Relson
2001-12-22  0:52     ` Mike Castle
2001-12-22  5:19     ` Craig I. Hagan
2001-12-22  8:15   ` Daniel Phillips
2001-12-21 21:09 ` David Gomez
2001-12-22  4:12   ` John Alvord
2001-12-22 18:12     ` David A. Frantz
2001-12-22 23:05       ` Alan Cox
2001-12-22  5:45   ` Bernd Eckenfels
  -- strict thread matches above, loose matches on Subject: below --
2001-12-21 16:45 Marcelo Tosatti
2001-12-21 19:13 ` Steven Spence
2001-12-21 19:15 ` Steven Spence
2001-12-22 11:56 ` Mike Black
2001-12-22 17:59   ` Stephan von Krawczynski
2001-12-22 23:41     ` J.A. Magallon

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=3C23B0AF.311FE86A@ixiacom.com \
    --to=dkegel@ixiacom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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