From: "Frank Filz" <ffilzlnx@mindspring.com>
To: "'Bruce Fields'" <bfields@fieldses.org>
Cc: "'Kernel NFS List'" <linux-nfs@vger.kernel.org>,
"'Ganesha NFS List'" <nfs-ganesha-devel@lists.sourceforge.net>
Subject: RE: pynfs updates
Date: Wed, 2 Oct 2013 11:58:52 -0400 [thread overview]
Message-ID: <00f701cebf88$4b8a37d0$e29ea770$@mindspring.com> (raw)
In-Reply-To: <20131002113607.GA7906@fieldses.org>
> > The new branch is here:
> >
> > https://github.com/ffilz/pynfs/commits/master
>
> Pulled, thanks!
And thank you. Bakeathon was very productive for Ganesha in this department.
We went from 34 failures to 10 failures.
Thanks
Frank
next prev parent reply other threads:[~2013-10-02 15:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 18:17 pynfs updates Frank Filz
2013-09-30 22:11 ` Bruce Fields
2013-09-30 23:54 ` Frank Filz
2013-10-01 14:26 ` 'Bruce Fields'
2013-10-01 14:30 ` 'Bruce Fields'
2013-10-01 15:42 ` Frank Filz
2013-10-01 19:05 ` Frank Filz
2013-10-02 11:36 ` 'Bruce Fields'
2013-10-02 15:58 ` Frank Filz [this message]
2013-10-01 18:21 ` Frank Filz
2013-10-01 18:45 ` 'Bruce Fields'
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='00f701cebf88$4b8a37d0$e29ea770$@mindspring.com' \
--to=ffilzlnx@mindspring.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=nfs-ganesha-devel@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).