From: Remco van 't Veer <remco@remworks.net>
To: guix-devel@gnu.org
Cc: Maxime Devos <maximedevos@telenet.be>,
Tobias Geerinckx-Rice <me@tobias.gr>
Subject: stalled ruby MRI patches
Date: Mon, 15 Aug 2022 15:26:50 +0200 [thread overview]
Message-ID: <87edxhab8l.fsf@remworks.net> (raw)
Hi,
A couple of weeks ago I submitted patches to the ruby MRI packages to
update them because the current versions have several CVEs leaning on
them;
- https://issues.guix.gnu.org/56301
- https://issues.guix.gnu.org/56302
- https://issues.guix.gnu.org/56303
- https://issues.guix.gnu.org/56304
Maxime Devos and Tobias Geerinckx-Rice already looked at them, I learned
about "grafs" and "replace", and made a v2 but there doesn't seem to
have been any progress since.
Is there anything I can do to help this along? Are there better ways to
promote patches (apart from being annoying on this mailinglist)?
Cheers,
Remco
reply other threads:[~2022-08-15 16:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87edxhab8l.fsf@remworks.net \
--to=remco@remworks.net \
--cc=guix-devel@gnu.org \
--cc=maximedevos@telenet.be \
--cc=me@tobias.gr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).