From: GOTO Masanori <gotom@debian.or.jp>
To: Jochen Hein <jochen@jochen.org>
Cc: Andries.Brouwer@cwi.nl, linux-kernel@vger.kernel.org,
akpm@osdl.org, torvalds@osdl.org
Subject: Re: [uPATCH] ufs.txt update
Date: Tue, 27 Jan 2004 14:09:22 +0900 [thread overview]
Message-ID: <81ektm9dvh.wl@omega.webmasters.gr.jp> (raw)
In-Reply-To: <87u12ksac2.fsf@echidna.jochen.org>
At Sun, 25 Jan 2004 09:26:21 +0100,
Jochen Hein wrote:
> Andries.Brouwer@cwi.nl writes:
>
> > old old format of ufs
> > - default value, supported os read-only
> > + supported os read-only
>
> s/os/as/ ?
>
> > 44bsd used in FreeBSD, NetBSD, OpenBSD
> > supported os read-write
>
> s/os/as/ ?
Exactly. In addition I think removing "default value" from "old"
entry is no effectiveness, so I revive this sentence.
This patch updates typos and HP-UX description in
Documentation/filesystems/ufs.txt, suggested by Andries.Brouwer@cwi.nl
and Jochen Hein <jochen@jochen.org>.
Regards,
-- gotom
--- Documentation/filesystems/ufs.txt 2003-07-28 02:06:11.000000000 +0900
+++ Documentation/filesystems/ufs.txt.new 2004-01-27 12:47:08.000000000 +0900
@@ -15,10 +15,10 @@
ufs manually by mount option ufstype. Possible values are:
old old format of ufs
- default value, supported os read-only
+ default value, supported as read-only
44bsd used in FreeBSD, NetBSD, OpenBSD
- supported os read-write
+ supported as read-write
sun used in SunOS (Solaris)
supported as read-write
@@ -26,6 +26,9 @@
sunx86 used in SunOS for Intel (Solarisx86)
supported as read-write
+ hp used in HP-UX
+ supported as read-only
+
nextstep
used in NextStep
supported as read-only
next prev parent reply other threads:[~2004-01-27 5:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-25 0:35 [uPATCH] ufs.txt update Andries.Brouwer
2004-01-25 8:26 ` Jochen Hein
2004-01-27 5:09 ` GOTO Masanori [this message]
2004-01-27 6:13 ` Frédéric L. W. Meunier
2004-01-27 10:33 ` szonyi calin
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=81ektm9dvh.wl@omega.webmasters.gr.jp \
--to=gotom@debian.or.jp \
--cc=Andries.Brouwer@cwi.nl \
--cc=akpm@osdl.org \
--cc=jochen@jochen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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