public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Laurence Perkins <lperkins@openeye.net>
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] Upgrading from 5.14 to 6.0 version
Date: Fri, 11 Nov 2022 18:12:22 +0000	[thread overview]
Message-ID: <MW2PR07MB4058F6EBC0E949C31335D8FBD2009@MW2PR07MB4058.namprd07.prod.outlook.com> (raw)
In-Reply-To: <CAJjrzcUvN_qNnbv5uO4+=hL4e=M9dRTLxTJX_hqUusJyha9cUA@mail.gmail.com>



> -----Original Message-----
> From: Arve Barsnes <arve.barsnes@gmail.com> 
> Sent: Friday, November 11, 2022 2:36 AM
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] Upgrading from 5.14 to 6.0 version
> 
> On Fri, 11 Nov 2022 at 11:30, Peter Humphrey <peter@prh.myzen.co.uk> wrote:
> > I can't remember any difficulty going from the 5 series to 6.0.0 
> > either, even though it was a .0 version, which we all know is generally to be suspected.
> 
> Not when it comes to the linux kernel though, where major version changes are arbitrary and comes around the x.19/20/21 switch no matter which new features are in it.
> 
> Regards,
> Arve
> 
> 
I can respect the fact that they've decided to increment it more often since the code is changing so much, but the 2.x to 3.x switch really should have been when they decided to drop support for the 80386 processor, and they deprecate and drop things more than often enough these days that they could easily tie it to that rather than having it be arbitrary, and therefore meaningless.

Where it's a kernel it doesn't have to break everything for everyone to justify incrementing the major.  Breaking something for somebody would be sufficient.

LMP

  parent reply	other threads:[~2022-11-11 18:12 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11  6:25 [gentoo-user] Upgrading from 5.14 to 6.0 version Dale
2022-11-11 10:30 ` Peter Humphrey
2022-11-11 10:35   ` Arve Barsnes
2022-11-11 10:56     ` Wols Lists
2022-11-11 18:12     ` Laurence Perkins [this message]
2022-11-11 12:24 ` hitachi303
2022-11-11 19:18   ` Dale
2022-11-11 22:08     ` Dr Rainer Woitok
2022-11-11 14:41 ` Rich Freeman
2022-11-11 19:42   ` Dale
2022-11-11 18:04 ` Laurence Perkins
2022-11-12 12:08 ` ralfconn
2022-11-12 16:00 ` [gentoo-user] " Nikos Chantziaras
2022-11-12 18:22   ` Dale
2022-11-12 18:43     ` Mark Knecht
2022-11-12 19:13     ` Wol
2022-11-12 20:02       ` Nikos Chantziaras
2022-11-12 20:03       ` Mark Knecht
2022-11-12 21:37         ` Dale
2022-11-14 19:57           ` Nikos Chantziaras
2022-11-14 21:05             ` Dale
2022-11-14 21:44               ` Michael
2022-11-14 23:56                 ` Wol
2022-11-15  0:10                 ` Dale
2022-11-15 17:46                   ` Laurence Perkins
2022-11-15  2:36                 ` Grant Edwards
2022-11-14 21:44               ` Mark Knecht
2022-11-12 21:17       ` Rich Freeman
2022-11-21  6:10 ` [gentoo-user] " Dale
2022-11-21 12:20   ` Rich Freeman
2022-11-21 20:52     ` Dale
2022-11-21 16:11   ` [gentoo-user] " Grant Edwards
2022-11-21 16:27     ` Michael
2022-11-21 16:50       ` Grant Edwards
2022-11-21 17:24         ` Michael
2022-11-21 18:12           ` Grant Edwards
2022-11-21 19:26             ` Michael
2022-11-21 19:37               ` Grant Edwards
2022-11-21 21:30                 ` Frank Steinmetzger
2022-11-21 18:15           ` Laurence Perkins
2022-11-22 19:01             ` Wol
2022-11-21 16:58     ` Mark Knecht
2022-11-21 17:49       ` Grant Edwards
2022-11-21 19:42         ` Mark Knecht

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=MW2PR07MB4058F6EBC0E949C31335D8FBD2009@MW2PR07MB4058.namprd07.prod.outlook.com \
    --to=lperkins@openeye.net \
    --cc=gentoo-user@lists.gentoo.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