From: Roland Mainz <roland.mainz@nrubsig.org>
To: cygwin-apps@cygwin.com
Subject: Fwd: Updating cygwin "libnfs" package ?
Date: Fri, 22 Mar 2024 17:08:35 +0100 [thread overview]
Message-ID: <CAKAoaQm+Etm6vAUZtwSRUPHBqmwAzz9uMYvfP4_OhozRsvYJLg@mail.gmail.com> (raw)
In-Reply-To: <ccab7df7-cca6-44ef-884e-ce2697896722@cornell.edu>
Hi!
----
I'd like to take ownership of the Cygwin "libnfs" package (see email
below, the package is old and has bugs related to NFSv4.*) ...
... how do we proceed ? Should I send a patch here, or what do I have to do ?
----
Bye,
Roland
---------- Forwarded message ---------
From: Ken Brown <kbrown@cornell.edu>
Date: Fri, Mar 22, 2024 at 4:36 PM
Subject: Re: Updating cygwin "libnfs" package ?
To: Roland Mainz <roland.mainz@nrubsig.org>, <cygwin@cygwin.com>
On 3/22/2024 9:49 AM, Roland Mainz via Cygwin wrote:
> Hi!
>
> ----
>
> Is it possible to update the Cygwin "libnfs" package, please ?
>
> The current Cygwin "libnfs" version is rather old (per
> https://cygwin.com/cgit/cygwin-packages/libnfs/log/
If you look near the upper right corner of that page, you'll see
"ORPHANED". See also
https://cygwin.com/packages/summary/libnfs-src.html .
That means there is no maintainer. So someone needs to volunteer to
maintain it before it will get updated. Are you interested in doing
this? If so, start at
https://cygwin.com/packages.html
and ask for help on the cygwin-apps mailing list if you run into problems.
Ken
--
__ . . __
(o.\ \/ /.o) roland.mainz@nrubsig.org
\__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer
/O /==\ O\ TEL +49 641 3992797
(;O/ \/ \O;)
next parent reply other threads:[~2024-03-22 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKAoaQk1ofn+6e4LGsAbFLgPm_C9S6h_Pik8cTC=uVQ247d1xg@mail.gmail.com>
[not found] ` <ccab7df7-cca6-44ef-884e-ce2697896722@cornell.edu>
2024-03-22 16:08 ` Roland Mainz [this message]
2024-03-22 18:47 ` Jon Turney
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=CAKAoaQm+Etm6vAUZtwSRUPHBqmwAzz9uMYvfP4_OhozRsvYJLg@mail.gmail.com \
--to=roland.mainz@nrubsig.org \
--cc=cygwin-apps@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).