public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Newall <davidn@davidnewall.com>
To: Joe Perches <joe@perches.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: List of 404 URLs in kernel .c and .h files
Date: Wed, 25 Feb 2009 12:11:39 +1030	[thread overview]
Message-ID: <49A4A1D3.8070402@davidnewall.com> (raw)
In-Reply-To: <1235506239.2501.46.camel@localhost>

Joe Perches wrote:
> Any suggestions on what if anything should be done
> to the sources with these dead links?

Unless you have a better reference, leave them.  Even if they 404, they
still provide a good starting point to search.

  parent reply	other threads:[~2009-02-25  1:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-24 20:10 List of 404 URLs in kernel .c and .h files Joe Perches
2009-02-24 21:23 ` Randy Dunlap
2009-02-24 21:38   ` Joe Perches
2009-02-25  8:30   ` Alex Chiang
2009-02-25 20:22     ` Martin Mares
2009-02-24 22:22 ` [PATCH] crypto: Fix dead links Adrian-Ken Rueegsegger
2009-03-07 10:45   ` Herbert Xu
2009-02-25  1:41 ` David Newall [this message]
2009-02-25  6:57   ` List of 404 URLs in kernel .c and .h files Sitsofe Wheeler
2009-02-25  9:24     ` David Newall

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=49A4A1D3.8070402@davidnewall.com \
    --to=davidn@davidnewall.com \
    --cc=joe@perches.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