From: Ben Dooks <ben-lkinux@fluff.org>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] Documentation/sparse snapshot URL
Date: Thu, 1 Sep 2005 21:30:06 +0100 [thread overview]
Message-ID: <20050901203006.GA17740@home.fluff.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 113 bytes --]
The URL for Documentation/sparse is wrong now that it is
in git.
Signed-off-by: Ben Dooks <ben-linux@fluff.org>
[-- Attachment #2: sparse-git-place.patch --]
[-- Type: text/plain, Size: 468 bytes --]
diff -urN -X ../dontdiff linux-2.6.13/Documentation/sparse.txt linux-2.6.13-bjd1/Documentation/sparse.txt
--- linux-2.6.13/Documentation/sparse.txt 2005-06-17 20:48:29.000000000 +0100
+++ linux-2.6.13-bjd1/Documentation/sparse.txt 2005-09-01 21:28:27.000000000 +0100
@@ -57,7 +57,7 @@
and DaveJ has tar-balls at
- http://www.codemonkey.org.uk/projects/bitkeeper/sparse/
+ http://www.codemonkey.org.uk/projects/git-snapshots/sparse/
Once you have it, just do
reply other threads:[~2005-09-01 20:30 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=20050901203006.GA17740@home.fluff.org \
--to=ben-lkinux@fluff.org \
--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 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®