All of lore.kernel.org
 help / color / mirror / Atom feed
From: ablacktshirt@gmail.com (Yubin Ruan)
To: kernelnewbies@lists.kernelnewbies.org
Subject: version number of Linux kernel development
Date: Tue, 1 Aug 2017 12:35:55 +0800	[thread overview]
Message-ID: <20170801043555.GA15511@HP> (raw)

Hi, 
I got a question regarding to Linux's version number. According to some talk
from Greg KH, there would be an accompanying stable release along with every
-rc release, that is, something like this:

         4.2.0
          |       \
    4.3.1-rc    4.2.1
          |        |
    4.3.2-rc     4.2.2
          |        |
    4.3.3-rc     4.2.3
          |        |
    4.3.4-rc     4.2.4
          |        |
    4.3.5-rc     4.2.5
          |        |
    4.3.6-rc     4.2.6
          |        |
    4.3.7-rc     4.2.7   <- this branch is thrown away after 4.4.0 is released
          |
    4.4.0

So, in this example, 4.2.7 would be thrown away after 4.4.0 is released. Is
this the same for every major release?

I see a series of 4.4.x release, ranging from 4.4.1 ~ 4.4.49,@
    http://elixir.free-electrons.com/linux/latest/source
which really confused me. Accoding to the model above, there should be only
4.4.7. After that, it would 4.5.x.

Please correct me if I am wrong.

Thanks,
Yubin

             reply	other threads:[~2017-08-01  4:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170801085256epcas4p4f0fcef4762795962ead0dbd69a341472@epcas4p4.samsung.com>
2017-08-01  4:35 ` Yubin Ruan [this message]
2017-08-01 10:06   ` version number of Linux kernel development Kamil Konieczny
2017-08-01 12:19   ` Kamil Konieczny

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=20170801043555.GA15511@HP \
    --to=ablacktshirt@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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.