From: Keith Owens <kaos@ocs.com.au>
To: jlmales@yahoo.com
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Question Regarding "EXTRAVERSION" Specification
Date: Thu, 06 Jun 2002 23:01:27 +1000 [thread overview]
Message-ID: <4708.1023368487@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Thu, 06 Jun 2002 03:09:29 -0400." <20020606030929.460bec3e.jlmales@softhome.net>
On Thu, 6 Jun 2002 03:09:29 -0400,
"John L. Males" <jlmales@softhome.net> wrote:
>***** Please note I am not on the Linux Kernel Mailing List. Please
>be so kind as to BCC copy me in on any reply to this inquiry. Thanks
>The questions are:
>
> 1) Is there a specification that states the maximum length that the
>"EXTRAVERSION" string may be?
The total length $(VERSION).$(PATCHLEVEL).$(SUBLEVEL)$(EXTRAVERSION)
must not exceed 64 characters. Break that limit and you get garbage in
uname -r.
> 2) Does the Kernel make/build process enforce any specified limit of
>(1) above?
kbuild 2.5 enforces the limit, the existing kernel build code does not.
I sent a patch to Linus four times back in the 2.4.15 days, he
completely ignored it. Linus does not care about kernel build
problems.
I will dig out the patch and send it to Marcelo.
next prev parent reply other threads:[~2002-06-06 13:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 7:09 Question Regarding "EXTRAVERSION" Specification John L. Males
2002-06-06 13:01 ` Keith Owens [this message]
2002-06-06 15:15 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2002-06-06 16:48 John L. Males
2002-06-06 17:12 ` John L. Males
2002-06-06 16:54 John L. Males
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=4708.1023368487@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=jlmales@yahoo.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 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.