All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Linus Torvalds <torvalds@osdl.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Linux/m68k <linux-m68k@lists.linux-m68k.org>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cross-sparse
Date: Sat, 19 Jun 2004 00:30:15 +0100	[thread overview]
Message-ID: <20040618233015.GA12063@redhat.com> (raw)
In-Reply-To: <20040618213338.GA4975@MAIL.13thfloor.at>

On Fri, Jun 18, 2004 at 11:33:38PM +0200, Herbert Poetzl wrote:

 > I did an 'extensive' search with google (you do not want 
 > to know how many hits you get with 'sparse') and read 
 > most postings on the sparse mailinglist (linux-sparse),
 > found the freshmeat project pointing me to the 'new url'
 > http://www.codemonkey.org.uk/projects/sparse/ where I can
 > download 'sparse-2003-11-27.tar.gz', then found out that
 > there should be a maintained (up to date) version of it at 
 > 
 >    http://www.kernel.org/pub/software/devel/sparse/
 > 
 > but what I find there, seems of no use to me ...
 > (I'm no bitkeeper person) so I'm still looking for an url
 > where I can get a recent .tar to install that beast.
 > 
 > can anybody point me in the right direction, please?

Erk, that's where I originally was snapshotting stuff, then
the box hosting codemonkey.org.uk died, and I had to restore
from backup. It turned a symlink to http://www.codemonkey.org.uk/projects/bitkeeper/sparse/
into a copy of the dir. Oops. I'll go fix that up (By just
killing the old dir).

		Dave


      parent reply	other threads:[~2004-06-18 23:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-17 21:13 [PATCH] cross-sparse Geert Uytterhoeven
2004-06-18 16:27 ` Linus Torvalds
2004-06-18 20:49   ` Geert Uytterhoeven
2004-06-18 20:58     ` Linus Torvalds
2004-06-19  0:33     ` viro
2004-06-18 21:33   ` Herbert Poetzl
2004-06-18 21:48     ` Randy.Dunlap
2004-06-18 21:57     ` Chris Wedgwood
2004-06-18 23:30     ` Dave Jones [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=20040618233015.GA12063@redhat.com \
    --to=davej@redhat.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=torvalds@osdl.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.