From: Steve Dickson <SteveD@RedHat.com>
To: Peter Wagner <tripolar@gmx.at>,
Chuck Lever <chuck.lever@oracle.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] nfs-utils: fix addrinfo usage with musl-1.1.21
Date: Tue, 19 Feb 2019 11:07:51 -0500 [thread overview]
Message-ID: <4df6f5e7-527f-4dae-02e5-11ca9ad67adf@RedHat.com> (raw)
In-Reply-To: <20190219100330.7679f4a3@onion.lan>
Hey Peter,
On 2/19/19 4:03 AM, Peter Wagner wrote:
> i updated to code to the latest version
Would you please create a new thread with
each patch version adding the version to
the subject line ex [PATCH V2].
It just make it much easier for me to
find the patch... tia,
steved.
prev parent reply other threads:[~2019-02-19 16:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-17 16:39 [PATCH] nfs-utils: fix addrinfo usage with musl-1.1.21 Peter Wagner
2019-02-17 17:40 ` Chuck Lever
2019-02-17 23:11 ` Peter Wagner
2019-02-18 2:21 ` Chuck Lever
2019-02-18 16:34 ` Steve Dickson
2019-02-18 17:00 ` Chuck Lever
2019-02-18 17:59 ` Steve Dickson
2019-02-18 18:23 ` Chuck Lever
2019-02-18 21:22 ` Peter Wagner
2019-02-18 21:26 ` Peter Wagner
2019-02-19 9:03 ` Peter Wagner
2019-02-19 14:52 ` Chuck Lever
2019-02-19 16:07 ` Steve Dickson [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=4df6f5e7-527f-4dae-02e5-11ca9ad67adf@RedHat.com \
--to=steved@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=tripolar@gmx.at \
/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 NNTP newsgroup(s).