public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: steved@redhat.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/3] Three more nfs-utils clean ups
Date: Tue, 06 Jan 2009 18:22:38 -0500	[thread overview]
Message-ID: <20090106231909.24661.92964.stgit@ingres.1015granger.net> (raw)

Hi Steve-

While digging through the last set of bugs in 2008, I constructed
these three fairly simple patches.  The middle one is probably the
most interesting, as it provides a little more flexibility about
how nfs-utils is built when libtirpc is present on the build system.

---

Chuck Lever (3):
      showmount command: Quiesce warning when TI-RPC is disabled
      configure: Add new build option "--enable-tirpc"
      configure: Remove inet_ntop(3) check from configure.ac


 configure.ac                |   34 +++++++++++++++++++++++-----------
 utils/showmount/showmount.c |   14 +++++++-------
 2 files changed, 30 insertions(+), 18 deletions(-)

-- 
Chuck Lever <chuck.lever@oracle.com>

             reply	other threads:[~2009-01-06 23:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-06 23:22 Chuck Lever [this message]
     [not found] ` <20090106231909.24661.92964.stgit-07a7zB5ZJzbwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
2009-01-06 23:22   ` [PATCH 1/3] configure: Remove inet_ntop(3) check from configure.ac Chuck Lever
2009-01-06 23:22   ` [PATCH 2/3] configure: Add new build option "--enable-tirpc" Chuck Lever
2009-01-06 23:22   ` [PATCH 3/3] showmount command: Quiesce warning when TI-RPC is disabled Chuck Lever
2009-01-07 17:54   ` [PATCH 0/3] Three more nfs-utils clean ups 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=20090106231909.24661.92964.stgit@ingres.1015granger.net \
    --to=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=steved@redhat.com \
    /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