From: Calum Mackay <calum.mackay@oracle.com>
To: "Aurélien Couderc" <aurelien.couderc2002@gmail.com>,
linux-nfs@vger.kernel.org, "Chuck Lever" <chuck.lever@oracle.com>
Cc: Calum Mackay <calum.mackay@oracle.com>
Subject: Re: pynfs-0.5 tagged and pushed
Date: Fri, 27 Mar 2026 19:08:12 +0000 [thread overview]
Message-ID: <941d32c3-afec-476d-8962-543e34beb3e8@oracle.com> (raw)
In-Reply-To: <CA+1jF5pguuUukL+5im41x0OewGX+kTtjFNEF3VD0g7nCC47XhA@mail.gmail.com>
On 27/03/2026 4:26 pm, Aurélien Couderc wrote:
> On Fri, Mar 27, 2026 at 3:47 PM Aurélien Couderc
> <aurelien.couderc2002@gmail.com> wrote:
>>
>> On Fri, Mar 27, 2026 at 3:57 AM Calum Mackay <calum.mackay@oracle.com> wrote:
>>>
>>> I've applied most of the outstanding pynfs patches, and tagged and
>>> pushed pynfs-0.5
>>>
>>> There were a couple of patches with which I'm having difficulties in
>>> testing, and I've emailed the authors.
>>>
>>> If you have submitted a pynfs patch which doesn't appear below, and I've
>>> not contacted you, apologies, and would you please let me know.
>>
>> @Chuck Lever wanted to contribute a test to set an ACL-on-file-create
>> and ACL-on-dir-create.
>> Was this never submitted?
hi Aurélien,
This is one of the patches with which I'm having test failures; no doubt
an issue with my test setup. I'll apply it as soon as we get that sorted
out.
thanks again,
calum.
>
> Forgot to CC Chuck Lever
>
> Aurélien
next prev parent reply other threads:[~2026-03-27 19:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 2:57 pynfs-0.5 tagged and pushed Calum Mackay
2026-03-27 14:47 ` Aurélien Couderc
2026-03-27 16:26 ` Aurélien Couderc
2026-03-27 19:08 ` Calum Mackay [this message]
2026-04-28 8:44 ` Aurélien Couderc
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=941d32c3-afec-476d-8962-543e34beb3e8@oracle.com \
--to=calum.mackay@oracle.com \
--cc=aurelien.couderc2002@gmail.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.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).