mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nick.Holloway@pyrites.org.uk (Nick Holloway)
To: linux-kernel@vger.kernel.org
Subject: Re: Change of policy for future 2.2 driver submissions
Date: 6 Jan 2001 10:15:53 -0000	[thread overview]
Message-ID: <936r8p$3ns$1@alfie.demon.co.uk> (raw)
In-Reply-To: <862569CB.0070DDEE.00@smtpnotes.altec.com>

In <862569CB.0070DDEE.00@smtpnotes.altec.com> Wayne.Brown@altec.com writes:
> Either I'm blind, or especially dense today, or both (quite possible :-) but I
> don't see any reference in patch-kernel to the extra version information.
> EXTRAVERSION is defined in the kernel Makefile, and I tried using the script
> found in the 2.4.0-test1 source like this:
> 
> patch-kernel /usr/src/linux /pub/linux/kernel/v2.4/test-kernels
> 
> but the test-2 and following patches are not applied.  All I get is "Current
> kernel version is 2.4.0."  What am I missing?

The distributed version of patch-kernel has only ever known about the
"standard" progression x.y.z => x.y.z+1.  This all gets horribly broken
when Linus gets imaginative with his kernel numbering.

I have said before that I thought this was OK, because the people that
need to cope with the EXTRAVERSION guff are people on the development
branch, and should be able to patch the kernel themselves.  The main
users of patch-kernel are less experienced people.

However, this does conflict with the aim of getting users into testing
kernels late in the development branch cycle.  It also affects people
like me who are lazy.

I don't think that getting the kernel version to support the naming scheme
du-jour will work, as this would require Linus to update patch-kernel
when he dreams up a new scheme -- and Linus is the one person I'm fairly
sure does not use it!

For myself, I have a version of patch-kernel that does know how to deal
with the wacky naming versions (because I'm lazy).  In future I'll make
this available to anyone that wants to download it for their own use,
but I won't push to get it included.

A (temporary) location for the current version is:

	http://www.alfie.demon.co.uk/download/patch-kernel

-- 
 `O O'  | Nick.Holloway@pyrites.org.uk
// ^ \\ | http://www.pyrites.org.uk/
-
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/

  reply	other threads:[~2001-01-06 10:16 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-05 20:33 Wayne.Brown
2001-01-06 10:15 ` Nick Holloway [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 17:32 Wayne.Brown
2001-01-05 18:50 ` Matthew D. Pitts
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='936r8p$3ns$1@alfie.demon.co.uk' \
    --to=nick.holloway@pyrites.org.uk \
    --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

all inboxes | Powered by JetHome®