From: Greg KH <gregkh@linuxfoundation.org>
To: Chris Jones <chrisjones@spin.net.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Custom kernel version numbers
Date: Fri, 22 Jun 2012 19:55:20 -0700 [thread overview]
Message-ID: <20120623025520.GB18260@kroah.com> (raw)
In-Reply-To: <4FE4F0DA.6080304@spin.net.au>
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.
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?
greg k-h
next prev parent reply other threads:[~2012-06-23 2:55 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 [this message]
2012-06-23 9:22 ` Chris Jones
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=20120623025520.GB18260@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=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