From: Jon Turney <jon.turney@dronecode.org.uk>
To: Roland Mainz <roland.mainz@nrubsig.org>
Cc: cygwin-apps@cygwin.com
Subject: Re: Fwd: Updating cygwin "libnfs" package ?
Date: Fri, 22 Mar 2024 18:47:28 +0000 [thread overview]
Message-ID: <b3c45a94-576c-4c6d-a039-fac649abb7ad@dronecode.org.uk> (raw)
In-Reply-To: <CAKAoaQm+Etm6vAUZtwSRUPHBqmwAzz9uMYvfP4_OhozRsvYJLg@mail.gmail.com>
On 22/03/2024 16:08, Roland Mainz via Cygwin-apps wrote:
> 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 ?
[1] should explain this (could probably be improved).
A patch against the packaging repo would be a good place to start.
[1] https://cygwin.com/packaging-contributors-guide.html#adopt
prev parent reply other threads:[~2024-03-22 18:47 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
2024-03-22 18:47 ` Jon Turney [this message]
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=b3c45a94-576c-4c6d-a039-fac649abb7ad@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
--cc=roland.mainz@nrubsig.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 read-only IMAP folder(s) and NNTP newsgroup(s).