From: ericvh@ericvh.myip.org (Eric Van Hensbergen)
To: linux-kernel@vger.kernel.org
Cc: v9fs-developer@lists.sourceforge.net
Subject: [PATCH] v9fs: minor documentation revisions
Date: Mon, 3 Oct 2005 14:39:53 -0500 (CDT) [thread overview]
Message-ID: <20051003193953.7D5DA48B5@localhost.localdomain> (raw)
[PATCH] v9fs: minor documentation revisions
A few minor documentation revisions:
a) change debug documentation to use decimal instead of hexdecimal
debug codes (to match current code)
b) remove timeout option (which was removed from the code)
c) change bug-reporting method from sourceforge to bugzilla
Signed-off-by: Eric Van Hensbergen <ericvh@gmail.com>
---
commit ae0cee5ba09de6bbfcde6cf8a48e281b544a7d34
tree 7ffaf19d60455fabb0e06bb5cb017db857fc620e
parent eae57357841b0c6d3000e6de66195aa848ee93c9
author Eric Van Hensbergen <ericvh@gmail.com> Mon, 03 Oct 2005 14:35:55 -0500
committer Eric Van Hensbergen <ericvh@gmail.com> Mon, 03 Oct 2005 14:35:55 -0500
Documentation/filesystems/v9fs.txt | 24 +++++++++++-------------
1 files changed, 11 insertions(+), 13 deletions(-)
diff --git a/Documentation/filesystems/v9fs.txt b/Documentation/filesystems/v9fs.txt
--- a/Documentation/filesystems/v9fs.txt
+++ b/Documentation/filesystems/v9fs.txt
@@ -40,14 +40,14 @@ OPTIONS
offering several exported file systems.
debug=n specifies debug level. The debug level is a bitmask.
- 0x01 = display verbose error messages
- 0x02 = developer debug (DEBUG_CURRENT)
- 0x04 = display 9P trace
- 0x08 = display VFS trace
- 0x10 = display Marshalling debug
- 0x20 = display RPC debug
- 0x40 = display transport debug
- 0x80 = display allocation debug
+ 1 = display verbose error messages
+ 2 = developer debug (DEBUG_CURRENT)
+ 4 = display 9P trace
+ 8 = display VFS trace
+ 16 = display Marshalling debug
+ 32 = display RPC debug
+ 64 = display transport debug
+ 128 = display allocation debug
rfdno=n the file descriptor for reading with proto=fd
@@ -57,8 +57,6 @@ OPTIONS
port=n port to connect to on the remote server
- timeout=n request timeouts (in ms) (default 60000ms)
-
noextend force legacy mode (no 9P2000.u semantics)
uid attempt to mount as a particular uid
@@ -75,8 +73,7 @@ RESOURCES
=========
The Linux version of the 9P server, along with some client-side utilities
-can be found at http://v9fs.sf.net (along with a CVS repository of the
-development branch of this module). There are user and developer mailing
+can be found at http://v9fs.sf.net. There are user and developer mailing
lists here, as well as a bug-tracker.
For more information on the Plan 9 Operating System check out
@@ -91,5 +88,6 @@ STATUS
The 2.6 kernel support is working on PPC and x86.
-PLEASE USE THE SOURCEFORGE BUG-TRACKER TO REPORT PROBLEMS.
+PLEASE USE THE KERNEL BUGZILLA TO REPORT PROBLEMS. (http://bugzilla.kernel.org)
+
reply other threads:[~2005-10-03 19:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20051003193953.7D5DA48B5@localhost.localdomain \
--to=ericvh@ericvh.myip.org \
--cc=linux-kernel@vger.kernel.org \
--cc=v9fs-developer@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
Powered by JetHome