From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Chen Qi" <Qi.Chen@windriver.com>
Cc: Alexander Kanavin <alex.kanavin@gmail.com>,
openembedded-core@lists.openembedded.org,
Alexander Kanavin <alex@linutronix.de>
Subject: Re: [OE-core] [PATCH 01/52] ifupdown: update 0.8.43 -> 0.8.41
Date: Wed, 8 Feb 2023 10:42:50 +0100 [thread overview]
Message-ID: <20230208104250.7ef3107b@booty> (raw)
In-Reply-To: <91a725de-88b4-6dad-cd41-f6a44cd5d685@windriver.com>
Hi Chen, Alex,
On Wed, 8 Feb 2023 15:48:40 +0800
"Chen Qi" <Qi.Chen@windriver.com> wrote:
> Typo. It should be 0.8.39 -> 0.8.41
Thanks for noticing! I have fixed the message while applying to my
testing branch.
Alex, I also skipped "python3-sphinx: upgrade 6.0.0 -> 6.1.3" as I
already have a patch by Tim doing the same upgrade in my branch.
Best regards,
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2023-02-08 9:43 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 7:20 [PATCH 01/52] ifupdown: update 0.8.43 -> 0.8.41 Alexander Kanavin
2023-02-08 7:20 ` [PATCH 02/52] python3-pip: update 22.3.1 -> 23.0 Alexander Kanavin
2023-02-08 7:20 ` [PATCH 03/52] diffutils: update 3.8 -> 3.9 Alexander Kanavin
2023-02-08 7:20 ` [PATCH 04/52] mc: update 4.8.28 -> 4.8.29 Alexander Kanavin
2023-02-08 7:20 ` [PATCH 05/52] xf86-video-vmware: update 13.3.0 -> 13.4.0 Alexander Kanavin
2023-02-08 7:20 ` [PATCH 06/52] lttng-tools: update 2.13.8 -> 2.13.9 Alexander Kanavin
2023-02-08 7:20 ` [PATCH 07/52] rt-tests: update 2.4 -> 2.5 Alexander Kanavin
2023-02-08 7:20 ` [PATCH 08/52] apr: update 1.7.0 -> 1.7.2 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 09/52] apr-util: update 1.6.1 -> 1.6.3 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 10/52] glib-2.0: upgrade 2.74.4 -> 2.74.5 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 11/52] systemd: update 252.4 -> 252.5 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 12/52] cmake: upgrade 3.25.1 -> 3.25.2 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 13/52] python3-setuptools: update 65.7.0 -> 67.2.0 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 14/52] lighttpd: upgrade 1.4.67 -> 1.4.68 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 15/52] lsof: upgrade 4.96.5 -> 4.98.0 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 16/52] igt-gpu-tools: upgrade 1.26 -> 1.27.1 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 17/52] vulkan-headers: upgrade 1.3.236.0 -> 1.3.239.0 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 18/52] vulkan-loader: " Alexander Kanavin
2023-02-08 7:21 ` [PATCH 19/52] vulkan-tools: " Alexander Kanavin
2023-02-08 7:21 ` [PATCH 20/52] spirv-tools: " Alexander Kanavin
2023-02-08 7:21 ` [PATCH 21/52] glslang: " Alexander Kanavin
2023-02-08 7:21 ` [PATCH 22/52] spirv-headers: " Alexander Kanavin
2023-02-08 7:21 ` [PATCH 23/52] libxpm: upgrade 3.5.14 -> 3.5.15 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 24/52] rng-tools: upgrade 6.15 -> 6.16 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 25/52] fontconfig: upgrade 2.14.1 -> 2.14.2 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 26/52] btrfs-tools: upgrade 6.1.2 -> 6.1.3 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 27/52] ncurses: upgrade 6.3+20220423 -> 6.4 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 28/52] mpg123: upgrade 1.31.1 -> 1.31.2 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 29/52] python3-pycryptodomex: upgrade 3.16.0 -> 3.17 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 30/52] bind: upgrade 9.18.10 -> 9.18.11 Alexander Kanavin
2023-03-02 8:55 ` [OE-core] " Takayasu Ito
2023-02-08 7:21 ` [PATCH 31/52] libjpeg-turbo: upgrade 2.1.4 -> 2.1.5 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 32/52] pkgconf: upgrade 1.9.3 -> 1.9.4 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 33/52] python3-sphinx: upgrade 6.0.0 -> 6.1.3 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 34/52] python3-pycryptodome: upgrade 3.16.0 -> 3.17 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 35/52] python3-dtschema: upgrade 2022.12 -> 2023.1 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 36/52] ell: upgrade 0.55 -> 0.56 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 37/52] llvm: upgrade 15.0.6 -> 15.0.7 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 38/52] puzzles: upgrade to latest revision Alexander Kanavin
2023-02-08 7:21 ` [PATCH 39/52] msmtp: upgrade 1.8.22 -> 1.8.23 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 40/52] dpkg: upgrade 1.21.18 -> 1.21.19 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 41/52] shaderc: upgrade 2022.4 -> 2023.2 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 42/52] sysstat: upgrade 12.6.1 -> 12.6.2 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 43/52] piglit: upgrade to latest revision Alexander Kanavin
2023-02-08 7:21 ` [PATCH 44/52] ltp: upgrade 20220930 -> 20230127 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 45/52] linux-firmware: upgrade 20221214 -> 20230117 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 46/52] libinput: upgrade 1.22.0 -> 1.22.1 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 47/52] sudo: upgrade 1.9.12p1 -> 1.9.12p2 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 48/52] diffoscope: upgrade 230 -> 234 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 49/52] texinfo: upgrade 7.0.1 -> 7.0.2 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 50/52] stress-ng: upgrade 0.15.02 -> 0.15.03 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 51/52] libgit2: upgrade 1.5.0 -> 1.5.1 Alexander Kanavin
2023-02-08 7:21 ` [PATCH 52/52] python3-pathspec: upgrade 0.10.3 -> 0.11.0 Alexander Kanavin
2023-02-08 7:48 ` [OE-core] [PATCH 01/52] ifupdown: update 0.8.43 -> 0.8.41 ChenQi
2023-02-08 9:42 ` 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=20230208104250.7ef3107b@booty \
--to=luca.ceresoli@bootlin.com \
--cc=Qi.Chen@windriver.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