From: Wayne.Brown@altec.com
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: phillips@innominate.de (Daniel Phillips),
hahn@coffee.psychology.mcmaster.ca (Mark Hahn),
linux-kernel@vger.kernel.org
Subject: Re: Change of policy for future 2.2 driver submissions
Date: Fri, 5 Jan 2001 11:32:39 -0600 [thread overview]
Message-ID: <862569CB.0060544C.00@smtpnotes.altec.com> (raw)
Well, I got off linux-kernel while 2.0.3x was still current, and didn't return
until a few months ago. Apparently the definitions have changed over the past
few years.
On another subject, is all this new "testXX-preYY" stuff over now that 2.4.0 is
out, and will we be going back to the standard x.y.z numbering scheme? Or is
this another thing that's changed for good? I really miss being able to apply
all the patches at once with linux/scripts/patchkernel.
Wayne
Alan Cox <alan@lxorguk.ukuu.org.uk> on 01/05/2001 11:15:36 AM
To: Wayne Brown/Corporate/Altec@Altec
cc: phillips@innominate.de (Daniel Phillips),
hahn@coffee.psychology.mcmaster.ca (Mark Hahn),
linux-kernel@vger.kernel.org
Subject: Re: Change of policy for future 2.2 driver submissions
> In other words, there's no longer any such thing as a "stable" branch. The
> whole point of having separate production and development branches was to have
> one in which each succeeding patch could be counted upon to be more reliable
By your personal definition of stable 2.0.3x is the current stable kernel.
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-05 17:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-05 17:32 Wayne.Brown [this message]
2001-01-05 18:50 ` Change of policy for future 2.2 driver submissions Matthew D. Pitts
-- strict thread matches above, loose matches on Subject: below --
2001-01-08 15:36 Wayne.Brown
2001-01-08 4:52 Wayne.Brown
2001-01-08 11:07 ` David Weinehall
2001-01-05 20:33 Wayne.Brown
2001-01-06 10:15 ` Nick Holloway
2001-01-05 17:11 Wayne.Brown
2001-01-05 17:15 ` Alan Cox
2001-01-05 17:23 ` Christoph.Hellwig.
[not found] ` <hchÀcaldera.de>
2001-01-05 17:31 ` Alan Cox
2001-01-05 3:50 Michael D. Crawford
2001-01-05 8:29 ` Miles Lane
2001-01-05 17:31 ` Linus Torvalds
2001-01-09 14:49 ` Hubert Mantel
2001-01-09 14:54 ` Alan Cox
2001-01-09 23:49 ` Jakob Østergaard
2001-01-10 0:02 ` Linus Torvalds
2001-01-10 0:33 ` Ingo Molnar
2001-01-10 1:03 ` Andrea Arcangeli
2001-01-10 1:17 ` Ingo Molnar
2001-01-10 1:40 ` Andrea Arcangeli
2001-01-05 2:41 Alan Cox
2001-01-05 3:27 ` Nicholas Knight
2001-01-05 4:23 ` Mark Hahn
2001-01-05 12:52 ` Daniel Phillips
2001-01-05 6:38 ` Tim Riker
2001-01-05 6:57 ` Andre Tomt
2001-01-05 7:30 ` Gerhard Mack
2001-01-05 11:46 ` Rik van Riel
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=862569CB.0060544C.00@smtpnotes.altec.com \
--to=wayne.brown@altec.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hahn@coffee.psychology.mcmaster.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@innominate.de \
/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.