From: slymattz <slymattz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [DRAFT] nfs-utils: update to 2.8.2.
Date: Thu, 09 Jan 2025 15:10:31 +0100 [thread overview]
Message-ID: <20250109141031.47C2C21436@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-53784@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 516 bytes --]
New comment by slymattz on void-packages repository
https://github.com/void-linux/void-packages/pull/53784#issuecomment-2580306694
Comment:
Hi!
There's a competing [PR](https://github.com/void-linux/void-packages/pull/53467) that accommodates a rebuild against the newest version of libtripc-devel. The only difference in nfs-utils between our PRs is that mine keeps _musl-getservbyport.patch_ intact.
As soon as the musl-dracut thing gets resolved, should I drop my PR whatsoever or make any changes to it?
next prev parent reply other threads:[~2025-01-09 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-01 7:45 [PR PATCH] " Vaelatern
2025-01-09 14:10 ` slymattz [this message]
2025-01-09 14:12 ` slymattz
2025-01-09 19:33 ` Vaelatern
2025-01-09 19:33 ` [PR PATCH] [Closed]: " Vaelatern
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=20250109141031.47C2C21436@inbox.vuxu.org \
--to=slymattz@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).