From: Christoph Hellwig <hch@infradead.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Linux NFS Mailing List <nfs@lists.sourceforge.net>
Subject: Re: New NFS-RDMA Patchset
Date: Wed, 13 Jun 2007 04:40:56 +0100 [thread overview]
Message-ID: <20070613034056.GA17058@infradead.org> (raw)
In-Reply-To: <1181705928.6616.16.camel@heimdal.trondhjem.org>
On Tue, Jun 12, 2007 at 11:38:48PM -0400, Trond Myklebust wrote:
> On Tue, 2007-06-12 at 10:27 -0500, Tom Tucker wrote:
> > I have a new patchset that addresses almost all of the comments from the
> > last review. The patchset includes the transport switch and the rdma
> > transport driver. The patchset is rather large and has 33 patches. I'd
> > like some guidance as to whether I tar it up or just send them out.
> >
> > Thanks,
> > Tom
>
> If you are worried about the number of patches then there are 3 possible
> solutions:
>
> 1. Provide a link to a website which lists the patches in an easily
> reviewable format.
> 2. Put them up in a git tree, and send us a pointer
> 3. Just send us a pointer to the gitweb site for the git tree you
> set up in 2. above :-)
Gitweb is extremly painfull to review, the only thing even worse is
a git tree without gitweb :)
the only reasonable formats for a big pile of patches to review are
a tarball of patches or a patchseries sent to a mailinglist.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2007-06-13 3:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 15:27 New NFS-RDMA Patchset Tom Tucker
2007-06-13 3:38 ` Trond Myklebust
2007-06-13 3:40 ` Christoph Hellwig [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=20070613034056.GA17058@infradead.org \
--to=hch@infradead.org \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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