From: Chuck Lever <chuck.lever@oracle.com>
To: neilb@suse.de
Cc: nfs@lists.sourceforge.net
Subject: [PATCH 00/23]
Date: Sat, 28 Jul 2007 17:49:06 -0400 [thread overview]
Message-ID: <20070728213611.21871.4021.stgit@localhost.localdomain> (raw)
Hi Neil-
During my continuing effort to familiarize myself with the current mount.nfs
code base, I've run across some minor issues for which I've created a set of
patches. These refactor, clarify, and modernize some areas of mount and
umount operation.
As always, constructive comments are welcome from all.
I'm continuing to look at fg/bg and at building string-ified mounting. I am
focusing on these clean-ups and bug fixes because it is clear that mount.nfs
is what distributions will use now instead of the old util-linux mount. Thus
mount.nfs must work as well as or better than the old mount command before we
move forward with string-ified mount option handling.
--
corporate: <chuck dot lever at oracle dot com>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2007-07-28 21:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-28 21:49 Chuck Lever [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-29 23:58 [patch 00/23] Thomas Gleixner
2006-09-30 8:35 ` Andrew Morton
2006-09-30 19:17 ` Thomas Gleixner
2006-09-30 8:35 ` Andrew Morton
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=20070728213611.21871.4021.stgit@localhost.localdomain \
--to=chuck.lever@oracle.com \
--cc=neilb@suse.de \
--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 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.