Linux NFS development
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Le Rouzic <aime.le-rouzic@bull.net>
Cc: Varun Chandramohan <varunc@linux.vnet.ibm.com>,
	Chuck Lever <chuck.lever@oracle.com>,
	Frank S Filz <ffilz@us.ibm.com>,
	"J. Bruce Fields" <bfields@fieldses.org>,
	Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: Full IPv6 client and server support (kernel and user commands)
Date: Fri, 21 Nov 2008 06:25:39 -0500	[thread overview]
Message-ID: <49269AB3.3020106@RedHat.com> (raw)
In-Reply-To: <48F347B8.3010201@bull.net>

Le Rouzic wrote:
>   Hi,
>   My patches are based on Chuck 's ones for nfs-utils and kernel. So
> when those from Chuck
>   are committed I will need to review mines if always OK.
>   Steve Dickson is planning to integrate most of the mount and statd
> command changes done by Chuck for IPV6
>   in next package nfs-utils-1.1.4.
This is done and can be found in git://linux-nfs.org/nfs-utils git

Also note number of IPv6 orientated changes have been added and
will continue to be added  to both the libitrpc and rpcbind git 
trees found at:

git://git.infradead.org/~steved/libtirpc.git
git://git.infradead.org/~steved/rpcbind.git

steved.


  parent reply	other threads:[~2008-11-21 11:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-19 12:36 Full IPv6 client and server support (kernel and user commands) Le Rouzic
2008-09-24 16:51 ` J. Bruce Fields
2008-09-24 22:07   ` J. Bruce Fields
     [not found] ` <48DA228D.9040302@linux.vnet.ibm.com>
     [not found]   ` <C0657B95-8B13-4D0B-A1D5-B1CDDB1C4AA7@oracle.com>
     [not found]     ` <48DB4C1C.6000805@bull.net>
     [not found]       ` <48DB5D89.6000407@linux.vnet.ibm.com>
     [not found]         ` <48DB79A7.2080501@bull.net>
     [not found]           ` <48DB7C51.8000606@linux.vnet.ibm.com>
     [not found]             ` <54717A2D-9C8B-48EB-AAEF-D6F5FF60E0D5@oracle.com>
     [not found]               ` <48DC824F.6070701@linux.vnet.ibm.com>
     [not found]                 ` <48DC90BD.4070702@bull.net>
     [not found]                   ` <48DCB184.1030406@linux.vnet.ibm.com>
     [not found]                     ` <8B169994-A636-440A-AF7A-7E043D18385E@oracle.com>
     [not found]                       ` <48DDA945.7020800@linux.vnet.ibm.com>
     [not found]                         ` <48E06DAC.2030708@linux.vnet.ibm.com>
     [not found]                           ` <48E085A7.7040000@bull.net>
     [not found]                             ` <48E19A2E.7090005@linux.vnet.ibm.com>
     [not found]                               ` <48E62607.80809@bull.net>
     [not found]                                 ` <48F31FEF.4040907@linux.vnet.ibm.com>
     [not found]                                   ` <48F347B8.3010201@bull.net>
2008-11-21 11:25                                     ` Steve Dickson [this message]
     [not found]                                       ` <49269AB3.3020106-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2008-11-21 12:55                                         ` Le Rouzic
2008-11-21 15:10                                         ` Chuck Lever
2008-11-21 15:26                                           ` 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=49269AB3.3020106@RedHat.com \
    --to=steved@redhat.com \
    --cc=aime.le-rouzic@bull.net \
    --cc=bfields@fieldses.org \
    --cc=chuck.lever@oracle.com \
    --cc=ffilz@us.ibm.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=varunc@linux.vnet.ibm.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