From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Daniel Andersen <anddan@linux-user.net>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH-NEW] README - Explain new 2.6.xx.x bug-fix release numbering scheme
Date: Fri, 27 Aug 2004 12:14:25 -0400 [thread overview]
Message-ID: <412F5DE1.1030204@nortelnetworks.com> (raw)
In-Reply-To: <412F52FA.5060904@linux-user.net>
Daniel Andersen wrote:
> Feel free to comment and suggest changes to it, the whole point is to
> make it readable in a way that normal human beings can make some sense
> out of it. (Read: Your grandmother)
> + As of kernel 2.6.8 there was a bug-fix release numbering scheme
> + introduced. In such cases a fourth number is added to the release
> + version, eg. 2.6.8.1. When patching from a 2.6.xx(.x) release to a
> + newer version, patches are to be applied against the original
> + release, eg. 2.6.8 and not the bug-fix release 2.6.8.1.
Perhaps "When patching from 2.6.x.y to 2.6.x.(y+1), patches are to be applied
against 2.6.x, not 2.6.x.y."
Chris
prev parent reply other threads:[~2004-08-27 16:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 15:27 [PATCH-NEW] README - Explain new 2.6.xx.x bug-fix release numbering scheme Daniel Andersen
2004-08-27 16:14 ` Chris Friesen [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=412F5DE1.1030204@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=anddan@linux-user.net \
--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