From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Alexander Kanavin" <alex.kanavin@gmail.com>
Cc: Alexander Kanavin <alex@linutronix.de>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] apt: fix upstream version check
Date: Thu, 26 May 2022 09:44:47 +0200 [thread overview]
Message-ID: <20220526094447.0a0a20d1@melee> (raw)
In-Reply-To: <CANNYZj-1wyTZH5Qk3jNHvuH=qWne9MML712sCTvCwg+J0ubcUg@mail.gmail.com>
Hi Alex,
Il giorno Wed, 25 May 2022 13:01:23 +0200
"Alexander Kanavin" <alex.kanavin@gmail.com> ha scritto:
> I haven’t seen it written explicitly, it comes from what stable Debian
> releases actually carry. There’s no harm in having a check that’s too
> strict, but there is harm in updating to versions that are actually
> intended for testing or unstable (and that’s what 2.4 is).
Ok, thanks for the clarification!
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2022-05-26 7:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 17:36 [PATCH] apt: fix upstream version check Alexander Kanavin
2022-05-25 8:29 ` [OE-core] " Luca Ceresoli
2022-05-25 11:01 ` Alexander Kanavin
2022-05-26 7:44 ` Luca Ceresoli [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=20220526094447.0a0a20d1@melee \
--to=luca.ceresoli@bootlin.com \
--cc=alex.kanavin@gmail.com \
--cc=alex@linutronix.de \
--cc=openembedded-core@lists.openembedded.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