From: Andreas Schwab <schwab@suse.de>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] remove BK documentation
Date: Mon, 02 May 2005 01:57:53 +0200 [thread overview]
Message-ID: <jer7gqqz26.fsf@sykes.suse.de> (raw)
In-Reply-To: <20050501233441.GC3592@stusta.de> (Adrian Bunk's message of "Mon, 2 May 2005 01:34:41 +0200")
Adrian Bunk <bunk@stusta.de> writes:
> --- linux-2.6.12-rc2-mm2-full/fs/cifs/README.old 2005-04-09 19:08:06.000000000 +0200
> +++ linux-2.6.12-rc2-mm2-full/fs/cifs/README 2005-04-09 19:08:29.000000000 +0200
> @@ -32,9 +32,9 @@
> 6) make modules (or "make" if CIFS VFS not to be built as a module)
>
> For Linux 2.6:
> -1) Download the kernel (e.g. from http://www.kernel.org or from bitkeeper
> -at bk://linux.bkbits.net/linux-2.5) and change directory into the top
> -of the kernel directory tree (e.g. /usr/src/linux-2.5.73)
> +1) Download the kernel (e.g. from http://www.kernel.org
> +and change directory into the top of the kernel directory tree
> +(e.g. /usr/src/linux-2.5.73)
That lacks a closing paren now.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2005-05-01 23:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-01 23:34 [2.6 patch] remove BK documentation Adrian Bunk
2005-05-01 23:43 ` Jeff Garzik
2005-05-02 0:08 ` Adrian Bunk
2005-05-02 0:16 ` Jeff Garzik
2005-05-02 15:53 ` Valdis.Kletnieks
2005-05-02 16:28 ` Bill Davidsen
2005-05-02 17:06 ` Tommy Reynolds
2005-05-01 23:57 ` Andreas Schwab [this message]
2005-05-02 0:04 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2005-04-09 17:24 Adrian Bunk
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=jer7gqqz26.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.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 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.