From: Alexey Dobriyan <adobriyan@gmail.com>
To: Harald Welte <laforge@netfilter.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ip_conntrack_pptp: fix endian sparse warnings
Date: Thu, 22 Sep 2005 19:34:51 +0400 [thread overview]
Message-ID: <20050922153451.GA7519@mipter.zuzino.mipt.ru> (raw)
In-Reply-To: <20050922132833.GM26520@sunbeam.de.gnumonks.org>
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
to get latest sparse tree.
next prev parent reply other threads:[~2005-09-22 15:24 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 [this message]
2005-09-22 17:00 ` [PATCH] update Documentation/sparse.txt Harald Welte
2005-09-22 17:09 ` 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=20050922153451.GA7519@mipter.zuzino.mipt.ru \
--to=adobriyan@gmail.com \
--cc=laforge@netfilter.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;
as well as URLs for NNTP newsgroup(s).