mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Harald Welte <laforge@netfilter.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] update Documentation/sparse.txt
Date: Thu, 22 Sep 2005 19:00:09 +0200	[thread overview]
Message-ID: <20050922170009.GP26520@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <20050922153451.GA7519@mipter.zuzino.mipt.ru>

[-- Attachment #1: Type: text/plain, Size: 2152 bytes --]

On Thu, Sep 22, 2005 at 07:34:51PM +0400, Alexey Dobriyan wrote:
> On Thu, Sep 22, 2005 at 03:28:34PM +0200, Harald Welte wrote:
> > btw, where can I get the latest sparse release?
> > 
> > linux-2.6.14-rc2/Documentation/sparse.txt still points to a dead
> > directory at
> > http://www.codemonkey.org.uk/projects/git-snapshots/sparse/
> > which now seems to be 404.
> > 
> > Are there no snapshots available?  Didn't anyone convre the bitkeeper
> > repository to git or something else?  I'm a bit puzzled.
> 
> 
> I use
> 
> rsync -avz --progress --delete \
> 	rsync://rsync.kernel.org/pub/scm/devel/sparse/sparse.git/ \
> 	.git

Thanks.  Please consider this patch for the mainline kernel:


[DOCUMENTATION] sparse no longer uses bk, but git

Signed-off-by: Harald Welte <laforge@netfilter.org>

---
commit 37df3d8b065579042d32a866ae6a00cd57c5812b
tree dd0e013e4744201b2ae13b38e0186477fd2eb47d
parent 0410f33b62b892379270539b189577126ea56ffe
author Harald Welte <laforge@netfilter.org> Do, 22 Sep 2005 18:58:49 +0200
committer Harald Welte <laforge@netfilter.org> Do, 22 Sep 2005 18:58:49 +0200

 Documentation/sparse.txt |    9 ++-------
 1 files changed, 2 insertions(+), 7 deletions(-)

diff --git a/Documentation/sparse.txt b/Documentation/sparse.txt
--- a/Documentation/sparse.txt
+++ b/Documentation/sparse.txt
@@ -51,14 +51,9 @@ or you don't get any checking at all.
 Where to get sparse
 ~~~~~~~~~~~~~~~~~~~
 
-With BK, you can just get it from
-
-        bk://sparse.bkbits.net/sparse
-
-and DaveJ has tar-balls at
-
-	http://www.codemonkey.org.uk/projects/git-snapshots/sparse/
+With git, you can just get it from
 
+        rsync://rsync.kernel.org/pub/scm/devel/sparse/sparse.git
 
 Once you have it, just do
 
-- 
- Harald Welte <laforge@netfilter.org>                 http://netfilter.org/
============================================================================
  "Fragmentation is like classful addressing -- an interesting early
   architectural error that shows how much experimentation was going
   on while IP was being designed."                    -- Paul Vixie

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-09-22 17:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050921170539.GA10537@mipter.zuzino.mipt.ru>
2005-09-22 13:28 ` [PATCH] ip_conntrack_pptp: fix endian sparse warnings Harald Welte
2005-09-22 15:34   ` Alexey Dobriyan
2005-09-22 17:00     ` Harald Welte [this message]
2005-09-22 17:09       ` [PATCH] update Documentation/sparse.txt Randy.Dunlap
2005-09-22 18:19         ` Harald Welte

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=20050922170009.GP26520@sunbeam.de.gnumonks.org \
    --to=laforge@netfilter.org \
    --cc=adobriyan@gmail.com \
    --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®