From: Chris Jones <chrisjones@spin.net.au>
To: linux-kernel@vger.kernel.org
Subject: Re: Custom kernel version numbers
Date: Sat, 23 Jun 2012 19:22:20 +1000 [thread overview]
Message-ID: <4FE58ACC.3040006@spin.net.au> (raw)
In-Reply-To: <20120623025520.GB18260@kroah.com>
Greg KH wrote:
> On Sat, Jun 23, 2012 at 08:25:30AM +1000, Chris Jones wrote:
>> Is there a general rule against giving a version number to a custom
>> kernel if credit is given to the base kernel version?
> You have the code, you can number it however you want.
Would not want to offend anyone. And if I were to do that, I would
always put reference to what base kernel my custom kernel was built upon.
>
> But, if you want others to have some clue as to what kernel you are
> running for whatever reason (support, community help with problems,
> etc.) I would recommend using the kernel.org release numbers and adding
> onto that like all of the major Linux distros do already.
>
> What were you thinking of numbering your kernel?
I never got that far. Keeping the kernel version and just adding my own
version number to the end might be the way to go.
Cheers
--
Chris Jones @ kernel.devproject@gmail.com
and oracle.kerneldev@gmail.com
OpenSUSE Linux x86_64 (PC)|Android (Smartphone)|Windows 7 (Laptop)|Windows XP (Gaming)
Kernel developer|Lead Developer of SDL|Lead Developer of Nest Linux|Gamer and Emulator nut|Web Services|Digital Imaging Services
Controllers: Rapier V2 Gaming mouse|Logitech Precision|PS3 controller|XB360 controller|Logitech Attack 3 j/stick
Emulators: Fusion|Gens|ZSNES|Project64|PCSX-R|Stella|WinVICE|WinUAE
prev parent reply other threads:[~2012-06-23 9:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 22:25 Custom kernel version numbers Chris Jones
2012-06-23 2:55 ` Greg KH
2012-06-23 9:22 ` Chris Jones [this message]
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=4FE58ACC.3040006@spin.net.au \
--to=chrisjones@spin.net.au \
--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