From: Doug Nazar <nazard@nazar.ca>
To: Steve Dickson <SteveD@RedHat.com>, linux-nfs@vger.kernel.org
Subject: Re: ANNOUNCE: nfs-utils-2.4.2 released.
Date: Tue, 19 Nov 2019 15:54:48 -0500 [thread overview]
Message-ID: <455b1ca6-85b4-c8a2-d66d-389115c5b94d@nazar.ca> (raw)
In-Reply-To: <fd6a75d4-9b52-9c8f-9ad5-d01340fdb89e@RedHat.com>
On 2019-11-17 14:40, Steve Dickson wrote:
>> Also attached are a few printf formating fixes for 32 bit.
> My apologies... I did miss this patch in the last release, but the
> patch is now committed...
>
> I blame the American Halloween... the day the patch was posted! :-)
> Those darn spooks and goblins of getting in the way!! 8-)
I'm sure they're to blame... they always are getting into things... ;-)
My fault for not sending it separately, but there was another patch
attached to the last email to fix some printf formatting strings for 32
bit clients. Let me know if you'd prefer if I send it as a separate email.
Doug
next prev parent reply other threads:[~2019-11-19 20:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-17 17:47 ANNOUNCE: nfs-utils-2.4.2 released Doug Nazar
2019-11-17 19:40 ` Steve Dickson
2019-11-19 20:54 ` Doug Nazar [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-15 16:14 Steve Dickson
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=455b1ca6-85b4-c8a2-d66d-389115c5b94d@nazar.ca \
--to=nazard@nazar.ca \
--cc=SteveD@RedHat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.