From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: lsof 4.98.0?
Date: Sun, 05 Feb 2023 10:32:30 +0100 [thread overview]
Message-ID: <ad285826-d9b9-e2fc-6091-12758e77c42f@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 453 bytes --]
Hi,
I noticed that Peter ships 'lsof 4.95.0.linux' in next/master.
Since Adolf was so kind to convert the problematic 'libtirpc' in
https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=024220e4dfc5993d5d64abfced918340f729fe62
(cited: "With the build based on this patch installed lsof works
normally again."), can we push 'lsof 4.98.0'?
I'm just doing a (last) clean build for testing and then '4.98.0' would
be ready...
Best,
Matthias
reply other threads:[~2023-02-05 9:32 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ad285826-d9b9-e2fc-6091-12758e77c42f@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.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