public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Mike Black" <mblack@csihq.com>
To: "lkml" <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.17
Date: Sat, 22 Dec 2001 06:56:44 -0500	[thread overview]
Message-ID: <002701c18adf$b9f0f140$ac542341@cfl.rr.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0112211439390.7313-100000@freak.distro.conectiva>

My thanks to for Marcelo's efforts...but....

Is there any way we can get Marcelo, Rik, and Andrea to work together on the
"stable" version now (a Linux tribunal)?

If Rik and Andrea just send their patches to Marcelo can we get agreement on
one release version?
It would seem that it's time to converge for the sake of bringing some
stability & simplicity to 2.4.x

There's been way too much discussion/questions on the list from people
wondering which one to use.
I understand Linus' reluctance to incorporate but it just seems like it's
time to converge these branches.


  parent reply	other threads:[~2001-12-22 11:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-21 16:45 Linux 2.4.17 Marcelo Tosatti
2001-12-21 19:13 ` Steven Spence
2001-12-21 19:15 ` Steven Spence
2001-12-21 19:47 ` [PATCH] Linux 2.4.17 - compile error in drivers/video/aty/aty_base.c Tobias Ringstrom
2001-12-22 11:56 ` Mike Black [this message]
2001-12-22 17:59   ` Linux 2.4.17 Stephan von Krawczynski
2001-12-22 23:41     ` J.A. Magallon
  -- strict thread matches above, loose matches on Subject: below --
2001-12-21 20:16 Dan Kegel
2001-12-21 19:44 ` Marcelo Tosatti
2001-12-21 21:59   ` Dan Kegel
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

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='002701c18adf$b9f0f140$ac542341@cfl.rr.com' \
    --to=mblack@csihq.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