public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Paulo Marques <pmarques@grupopie.com>
Cc: trivial@kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 17/17]Documentation/blockdev/paride.txt update web address.
Date: Wed, 21 Jul 2010 06:38:08 -0700	[thread overview]
Message-ID: <4C46F840.6010908@gmail.com> (raw)
In-Reply-To: <4C46E289.6010009@grupopie.com>

On 07/21/2010 05:05 AM, Paulo Marques wrote:
> Justin P. Mattock wrote:
>> The patch below removes a web address due to me being unable
>> to locate this at all. If anybody knows the location let
>> me know and I'll resend.
>>
>> Signed-off-by: Justin P. Mattock<justinmattock@gmail.com>
>>
>> ---
>>   Documentation/blockdev/paride.txt |    5 -----
>>   1 files changed, 0 insertions(+), 5 deletions(-)
>>
>> diff --git a/Documentation/blockdev/paride.txt b/Documentation/blockdev/paride.txt
>> index e431267..11c4e3f 100644
>> --- a/Documentation/blockdev/paride.txt
>> +++ b/Documentation/blockdev/paride.txt
>> @@ -409,9 +409,4 @@ the list manager is a robot that will subscribe you using the reply
>>   address in your mail headers.  REMOVE any anti-spam gimmicks you may
>>   have in your mail headers, when sending mail to the list server.
>>
>> -You might also find some useful information on the linux-parport
>> -web pages (although they are not always up to date) at
>> -
>> -	http://www.torque.net/parport/
>> -
>
> I don't think removing an address like this is the best option. At least
> having the "old" address allows me to go to www.archive.org and find out
> a lot of useful information.
>
> Maybe just marking it as "(dead link)" and warning the respective
> maintainer would be better?
>


the whole tourque.net thing is dead.. it's not just this one here..
there must be at-least four or five of them throughout the Documentation.

is there a new updated location? or is www.archive.org already the new 
updated address?

Justin P. Mattock

  reply	other threads:[~2010-07-21 13:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-21  4:51 [PATCH 16/16]Documentation/binfmt_misc.txt update web address Justin P. Mattock
2010-07-21  4:51 ` [PATCH 17/17]Documentation/blockdev/paride.txt " Justin P. Mattock
2010-07-21 12:05   ` Paulo Marques
2010-07-21 13:38     ` Justin P. Mattock [this message]
2010-07-22  3:26       ` Randy Dunlap
2010-07-21  4:51 ` [PATCH 18/18]Documentation/cdrom/packet-writing.txt " Justin P. Mattock
2010-07-21  4:51 ` [PATCH 19/19]Documentation/cgroups/cpusets.txt fix typo in " Justin P. Mattock
2010-07-21  4:51 ` [PATCH 20/20]Documentation/development-process/4.Coding update " Justin P. Mattock
2010-07-21  4:51 ` [PATCH 21/21]Documentation/device-mapper/dm-crypt.txt " Justin P. Mattock
2010-07-21  4:51 ` [PATCH 22/22]Documentation/devices.txt " Justin P. Mattock
2010-07-21  4:51 ` [PATCH 23/23]Documentation/DocBook/v4l/fdl-appendix.xml " Justin P. Mattock
2010-07-21  4:52 ` [PATCH 24/24]Documentation/DocBook/v4l/compat.xml " Justin P. Mattock
2010-07-21  4:52 ` [PATCH 25/25]Documentation/DocBook/scsi.tmpl " Justin P. Mattock
2010-07-22  3:27   ` Randy Dunlap
2010-07-21  4:52 ` [PATCH 26/26]Documentation/dvb/faq.txt " Justin P. Mattock
2010-07-21  4:52 ` [PATCH 27/27]Documentation/dvb/get_dvb_firmware " Justin P. Mattock
2010-07-21  4:52 ` [PATCH 28/28]Documentation/fb/framebuffer.txt " Justin P. Mattock
2010-09-04 15:11   ` Geert Uytterhoeven
2010-09-04 15:57     ` Justin P. Mattock
2010-07-21  4:52 ` [PATCH 29/29]Documentation/filesystems/isofs.txt " Justin P. Mattock
2010-07-21  4:52 ` [PATCH 30/30]Documentation/filesystems/befs.txt " Justin P. Mattock

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=4C46F840.6010908@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmarques@grupopie.com \
    --cc=trivial@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