All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Jim Rees <rees@umich.edu>
Cc: linux-nfs@vger.kernel.org, peter honeyman <honey@citi.umich.edu>
Subject: Re: [PATCH] nfs-utils: Move common code into support
Date: Wed, 13 Oct 2010 10:21:51 -0400	[thread overview]
Message-ID: <4CB5C07F.2080902@RedHat.com> (raw)
In-Reply-To: <20101005202438.GA15113-8f4Pc2RrbJmHXe+LvDLADg@public.gmane.org>



On 10/05/2010 04:24 PM, Jim Rees wrote:
> This is a re-worked version of David P. Quigley's patch sent to the list on
> 22 Jun 2010.  I just made it apply against current source.
> 
> There are several source files and headers present in the ./utils/idmapd
> directory which are also usable in a doimapd daemon. Because of this we move
> that support into the support directory such that it can be shared by both
> daemons.
Committed...

steved.

      parent reply	other threads:[~2010-10-13 14:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-05 20:24 [PATCH] nfs-utils: Move common code into support Jim Rees
     [not found] ` <20101005202438.GA15113-8f4Pc2RrbJmHXe+LvDLADg@public.gmane.org>
2010-10-13 14:21   ` 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=4CB5C07F.2080902@RedHat.com \
    --to=steved@redhat.com \
    --cc=honey@citi.umich.edu \
    --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.