From: "Justin P. Mattock" <justinmattock@gmail.com>
To: trivial@kernel.org
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
"Justin P. Mattock" <justinmattock@gmail.com>
Subject: [PATCH 30/30]Documentation/filesystems/befs.txt update web address.
Date: Tue, 20 Jul 2010 21:52:06 -0700 [thread overview]
Message-ID: <1279687926-29360-15-git-send-email-justinmattock@gmail.com> (raw)
In-Reply-To: <1279687926-29360-1-git-send-email-justinmattock@gmail.com>
The patch below updates some broken web addresses.
Signed-off-by: Justin P. Mattock <justinmattock@gmail.com>
---
Documentation/filesystems/befs.txt | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/filesystems/befs.txt b/Documentation/filesystems/befs.txt
index 67391a1..6e49c36 100644
--- a/Documentation/filesystems/befs.txt
+++ b/Documentation/filesystems/befs.txt
@@ -31,7 +31,7 @@ Current maintainer: Sergey S. Kostyliov <rathamahata@php4.ru>
WHAT IS THIS DRIVER?
==================
-This module implements the native filesystem of BeOS <http://www.be.com/>
+This module implements the native filesystem of BeOS http://www.beincorporated.com/
for the linux 2.4.1 and later kernels. Currently it is a read-only
implementation.
@@ -61,7 +61,7 @@ step 2. Configuration & make kernel
The linux kernel has many compile-time options. Most of them are beyond the
scope of this document. I suggest the Kernel-HOWTO document as a good general
-reference on this topic. <http://www.linux.com/howto/Kernel-HOWTO.html>
+reference on this topic. http://www.linuxdocs.org/HOWTOs/Kernel-HOWTO-4.html
However, to use the BeFS module, you must enable it at configure time.
--
1.7.1.rc1.21.gf3bd6
prev parent reply other threads:[~2010-07-21 5:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 4:51 [PATCH 16/16]Documentation/binfmt_misc.txt " Justin P. Mattock
2010-07-21 4:51 ` [PATCH 17/17]Documentation/blockdev/paride.txt " Justin P. Mattock
2010-07-21 12:05 ` Paulo Marques
2010-07-21 13:38 ` Justin P. Mattock
2010-07-22 3:26 ` Randy Dunlap
2010-07-21 4:51 ` [PATCH 18/18]Documentation/cdrom/packet-writing.txt " Justin P. Mattock
2010-07-21 4:51 ` [PATCH 19/19]Documentation/cgroups/cpusets.txt fix typo in " Justin P. Mattock
2010-07-21 4:51 ` [PATCH 20/20]Documentation/development-process/4.Coding update " Justin P. Mattock
2010-07-21 4:51 ` [PATCH 21/21]Documentation/device-mapper/dm-crypt.txt " Justin P. Mattock
2010-07-21 4:51 ` [PATCH 22/22]Documentation/devices.txt " Justin P. Mattock
2010-07-21 4:51 ` [PATCH 23/23]Documentation/DocBook/v4l/fdl-appendix.xml " Justin P. Mattock
2010-07-21 4:52 ` [PATCH 24/24]Documentation/DocBook/v4l/compat.xml " Justin P. Mattock
2010-07-21 4:52 ` [PATCH 25/25]Documentation/DocBook/scsi.tmpl " Justin P. Mattock
2010-07-22 3:27 ` Randy Dunlap
2010-07-21 4:52 ` [PATCH 26/26]Documentation/dvb/faq.txt " Justin P. Mattock
2010-07-21 4:52 ` [PATCH 27/27]Documentation/dvb/get_dvb_firmware " Justin P. Mattock
2010-07-21 4:52 ` [PATCH 28/28]Documentation/fb/framebuffer.txt " Justin P. Mattock
2010-09-04 15:11 ` Geert Uytterhoeven
2010-09-04 15:57 ` Justin P. Mattock
2010-07-21 4:52 ` [PATCH 29/29]Documentation/filesystems/isofs.txt " Justin P. Mattock
2010-07-21 4:52 ` Justin P. Mattock [this message]
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=1279687926-29360-15-git-send-email-justinmattock@gmail.com \
--to=justinmattock@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@kernel.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
all inboxes | Powered by JetHome®