From: wundrweapon <wundrweapon@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] glibc: update to 2.34.
Date: Sat, 30 Jul 2022 18:16:38 +0200 [thread overview]
Message-ID: <20220730161638.dg48oJBYnXTn5y_IeIW1CE7Isisxz14oCVlOtm7DWUs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32330@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 243 bytes --]
New review comment by wundrweapon on void-packages repository
https://github.com/void-linux/void-packages/pull/32330#discussion_r933853985
Comment:
If you're updating to 2.35, do these not need to be adjusted as well? i.e. not point to 2.34
next prev parent reply other threads:[~2022-07-30 16:16 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 4:26 [PR PATCH] " ericonr
2021-08-05 4:26 ` [PR REVIEW] " ericonr
2021-08-05 4:31 ` [PR PATCH] [Updated] " ericonr
2021-08-05 4:37 ` ericonr
2021-08-05 15:18 ` ericonr
2022-02-15 6:43 ` JamiKettunen
2022-05-31 2:13 ` github-actions
2022-06-05 21:14 ` ericonr
2022-06-05 21:15 ` [PR PATCH] [Updated] " ericonr
2022-06-05 21:21 ` ericonr
2022-07-30 16:02 ` wundrweapon
2022-07-30 16:16 ` wundrweapon [this message]
2022-07-30 16:21 ` [PR REVIEW] " wundrweapon
2022-08-13 6:36 ` oreo639
2022-08-23 21:08 ` glibc: update to 2.35 oreo639
2022-09-22 13:45 ` AngryPhantom
2022-09-22 13:54 ` JamiKettunen
2022-09-22 14:14 ` AngryPhantom
2022-09-23 1:50 ` oreo639
2022-09-23 8:34 ` AngryPhantom
2022-09-23 8:41 ` oreo639
2022-09-23 8:41 ` oreo639
2022-09-23 8:42 ` oreo639
2022-09-23 8:44 ` oreo639
2022-09-23 8:46 ` oreo639
2022-09-23 8:46 ` AngryPhantom
2022-09-23 10:25 ` AngryPhantom
2022-09-23 11:17 ` AngryPhantom
2022-09-23 11:17 ` AngryPhantom
2022-09-23 11:36 ` AngryPhantom
2022-09-23 11:36 ` AngryPhantom
2022-09-23 16:59 ` oreo639
2023-01-11 13:12 ` [PR PATCH] [Closed]: " classabbyamp
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=20220730161638.dg48oJBYnXTn5y_IeIW1CE7Isisxz14oCVlOtm7DWUs@z \
--to=wundrweapon@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).