From: Christoph Hellwig <hch@infradead.org>
To: Jim Rees <rees@umich.edu>
Cc: Steve Dickson <SteveD@redhat.com>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfs-utils: Check for strlcat/cpy and compile our private version only if it's needed.
Date: Wed, 20 Oct 2010 22:14:37 -0400 [thread overview]
Message-ID: <20101021021437.GA5241@infradead.org> (raw)
In-Reply-To: <20101020213554.GA27541-8f4Pc2RrbJmHXe+LvDLADg@public.gmane.org>
Not that I'd complain, but what Linux libc provides strlcat/cpy?
next prev parent reply other threads:[~2010-10-21 2:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 21:35 [PATCH] nfs-utils: Check for strlcat/cpy and compile our private version only if it's needed Jim Rees
[not found] ` <20101020213554.GA27541-8f4Pc2RrbJmHXe+LvDLADg@public.gmane.org>
2010-10-21 2:14 ` Christoph Hellwig [this message]
2010-10-21 12:01 ` Jim Rees
2010-10-21 12:40 ` Christoph Hellwig
2010-10-28 13:40 ` Steve Dickson
2010-10-28 15:59 ` Jim Rees
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=20101021021437.GA5241@infradead.org \
--to=hch@infradead.org \
--cc=SteveD@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=rees@umich.edu \
/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.