From: "Matthew D. Pitts" <mpitts@suite224.net>
To: <Wayne.Brown@altec.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Change of policy for future 2.2 driver submissions
Date: Fri, 5 Jan 2001 13:50:26 -0500 [thread overview]
Message-ID: <004101c07748$60a74720$9842b0d1@pittscomp.com> (raw)
In-Reply-To: <862569CB.0060544C.00@smtpnotes.altec.com>
----- Original Message -----
From: <Wayne.Brown@altec.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Daniel Phillips <phillips@innominate.de>; Mark Hahn
<hahn@coffee.psychology.mcmaster.ca>; <linux-kernel@vger.kernel.org>
Sent: Friday, January 05, 2001 12:32 PM
Subject: Re: Change of policy for future 2.2 driver submissions
> 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
>
Wayne,
The versions of patch-kernel included in 2.3/2.4 support extra version
information, so patches from Linus and others (i.e. Alan Cox) can be applied
if proper information is placed in the kernel Makefile.
Matthew D. Pitts
mpitts@suite224.net
-
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 prev parent reply other threads:[~2001-01-05 18:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-05 17:32 Change of policy for future 2.2 driver submissions Wayne.Brown
2001-01-05 18:50 ` Matthew D. Pitts [this message]
-- 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='004101c07748$60a74720$9842b0d1@pittscomp.com' \
--to=mpitts@suite224.net \
--cc=Wayne.Brown@altec.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