linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Christoph Hellwig <hch@infradead.org>,
	linux-fsdevel@vger.kernel.org, nfs@lists.sourceforge.net
Subject: Re: [PATCH 0/18] export operations rewrite
Date: Mon, 7 May 2007 10:06:10 +1000	[thread overview]
Message-ID: <17982.28018.403942.663539@notabene.brown> (raw)
In-Reply-To: message from Neil Brown on Monday May 7

On Monday May 7, neilb@suse.de wrote:
> 
> Would you be able to respin that second patch series with one of those
> changes?

Of course it is actually the first series of patches that introduces
this problem.  So maybe just a full respin??

Thanks,
NeilBrown

-------------------------------------------------------------------------
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

  reply	other threads:[~2007-05-07  0:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-17  1:09 [PATCH 0/18] export operations rewrite Christoph Hellwig
2007-03-28 16:39 ` [NFS] " Christoph Hellwig
2007-03-30  3:34 ` Neil Brown
2007-05-01 10:39   ` [NFS] " Christoph Hellwig
2007-05-04  6:49     ` Neil Brown
2007-05-06 23:52       ` [NFS] " Neil Brown
2007-05-07  0:06         ` Neil Brown [this message]
2007-05-07  7:51           ` Christoph Hellwig
2007-05-13 20:41             ` Christoph Hellwig
2007-05-14  0:13               ` Neil Brown
2007-04-01 15:03 ` David Woodhouse
2007-05-13 20:43   ` [NFS] " Christoph Hellwig

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=17982.28018.403942.663539@notabene.brown \
    --to=neilb@suse.de \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=nfs@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).