public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	Markus Heiser <markus.heiser@darmarit.de>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 11/21] Documentation/kernel-docs.txt: convert it to ReST markup
Date: Fri, 16 Sep 2016 18:28:49 -0300	[thread overview]
Message-ID: <20160916182849.2a7101ea@vento.lan> (raw)
In-Reply-To: <20160916150009.21317711@lwn.net>

Em Fri, 16 Sep 2016 15:00:09 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:

> On Fri, 16 Sep 2016 17:42:19 -0300
> Mauro Carvalho Chehab <mchehab@s-opensource.com> wrote:
> 
> > > many of the links in it are long since
> > > dead, and I honestly doubt it has been helpful to anybody.    
> > 
> > I tested: all links there point to an existing documentation.  
> 
> Really?
> 
>  URL: http://plg.uwaterloo.ca/
>  URL: http://www.tldp.org/LDP/khg/HyperNews/get/khg.html

Those worked.

>  URL: ftp://ftp.llp.fu-berlin.de/pub/linux/LINUX-LAB/whitepapers/pcip.ps.gz
>  URL: ftp://ftp.llp.fu-berlin.de/pub/linux/LINUX-LAB/whitepapers/drivers.ps.gz
>  URL: ftp://ftp.uk.linux.org/pub/linux/sct/fs/jfs/journal-design.ps.gz
>  URL: http://usb.in.tum.de/usbdoc/
>  URL: http://www.linux-mag.com/1999-05/gear_01.html
>  URL: http://www.moses.uklinux.net/patches/lki.html
>  URL: http://www.edn.com/article/CA46968.html
>  URL: http://www.cse.unsw.edu.au/~neilb/oss/linux-commentary/nfsd.html 
>  URL: http://kt.earth.li/kernel-traffic/index.html
>  URL: http://edge.kernelnotes.org  /* linkspam site */
>  URL: http://www.tux.org/lkml/
>  URL: http://slencyclopedia.berlios.de/index.html
>  URL: http://marc.theaimsgroup.com/?l=linux-kernel
>  URL: http://www.cs.helsinki.fi/linux/linux-kernel/
>  URL: http://www.lib.uaa.alaska.edu/linux-kernel/

The above didn't.

> Do any of those links work for you?

Yeah, I looked on my browser history... I didn't checked all links here,
just a bunch of them. 

Sorry for the mess.

Feel free to just ignore patch 11, or if you prefer, we can just remove
the broken entries.

> 
> jon



Thanks,
Mauro

  reply	other threads:[~2016-09-16 21:29 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14 11:06 [PATCH v3 00/21] Create a book for Kernel development Mauro Carvalho Chehab
2016-09-14 11:06 ` [PATCH v3 01/21] doc: development-process: convert it to ReST markup Mauro Carvalho Chehab
2016-09-14 11:06 ` [PATCH v3 02/21] doc: development-process: rename files to rst Mauro Carvalho Chehab
2016-09-14 11:06 ` [PATCH v3 03/21] docs-rst: create a book for the development process Mauro Carvalho Chehab
2016-09-14 11:06 ` [PATCH v3 04/21] Documentation/HOWTO: convert to ReST notation Mauro Carvalho Chehab
2016-09-14 11:06 ` [PATCH v3 05/21] Documentation/applying-patches.txt: convert it to ReST markup Mauro Carvalho Chehab
2016-09-16 17:10   ` Jonathan Corbet
2016-09-16 17:20     ` Joe Perches
2016-09-16 21:36       ` Mauro Carvalho Chehab
2016-09-16 20:25     ` Mauro Carvalho Chehab
2016-09-14 11:06 ` [PATCH v3 06/21] Documentation/Changes: " Mauro Carvalho Chehab
2016-09-14 11:06 ` [PATCH v3 07/21] Documentation/CodingStyle: Convert " Mauro Carvalho Chehab
2016-09-16 17:13   ` Jonathan Corbet
2016-09-16 20:34     ` Mauro Carvalho Chehab
2016-09-17  9:58       ` Mauro Carvalho Chehab
2016-09-14 11:06 ` [PATCH v3 08/21] Documentation/CodingStyle: use the proper tag for verbatim font Mauro Carvalho Chehab
2016-09-14 11:06 ` [PATCH v3 09/21] Documentation/CodingStyle: replace underline markups Mauro Carvalho Chehab
2016-09-14 11:06 ` [PATCH v3 10/21] Documentation/CodingStyle: use the .. note:: markup where needed Mauro Carvalho Chehab
2016-09-14 11:06 ` [PATCH v3 11/21] Documentation/kernel-docs.txt: convert it to ReST markup Mauro Carvalho Chehab
2016-09-16 17:15   ` Jonathan Corbet
2016-09-16 20:42     ` Mauro Carvalho Chehab
2016-09-16 21:00       ` Jonathan Corbet
2016-09-16 21:28         ` Mauro Carvalho Chehab [this message]
2016-09-14 11:06 ` [PATCH v3 12/21] Documentation/ManagementStyle: " Mauro Carvalho Chehab
2016-09-14 11:06 ` [PATCH v3 13/21] Documentation/SecurityBugs: " Mauro Carvalho Chehab
2016-09-16 17:17   ` Jonathan Corbet
2016-09-16 20:53     ` Mauro Carvalho Chehab
2016-09-14 11:06 ` [PATCH v3 14/21] Documentation/stable_api_nonsense.txt: " Mauro Carvalho Chehab
2016-09-14 11:06 ` [PATCH v3 15/21] Documentation/stable_kernel_rules.txt: " Mauro Carvalho Chehab
2016-09-14 11:06 ` [PATCH v3 16/21] Documentation/SubmittingDrivers: " Mauro Carvalho Chehab
2016-09-14 11:06 ` [PATCH v3 17/21] Documentation/SubmittingPatches: " Mauro Carvalho Chehab
2016-09-16 17:21   ` Jonathan Corbet
2016-09-16 22:14     ` Mauro Carvalho Chehab
2016-09-14 11:06 ` [PATCH v3 18/21] Documentation/HOWTO: add cross-references to other documents Mauro Carvalho Chehab
2016-09-14 11:06 ` [PATCH v3 19/21] docs-rst: move HOWTO and mentioned documents to development-process/ Mauro Carvalho Chehab
2016-09-16 17:23   ` Jonathan Corbet
2016-09-14 11:06 ` [PATCH v3 21/21] doc-rst: Add the new development-process/ files to Sphinx build Mauro Carvalho Chehab

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=20160916182849.2a7101ea@vento.lan \
    --to=mchehab@s-opensource.com \
    --cc=corbet@lwn.net \
    --cc=jani.nikula@linux.intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus.heiser@darmarit.de \
    --cc=mchehab@infradead.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