From: Bill Davidsen <davidsen@tmr.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.27
Date: Fri, 14 Nov 2008 12:56:42 -0500 [thread overview]
Message-ID: <491DBBDA.6040105@tmr.com> (raw)
In-Reply-To: <491D99AE.90504@s5r6.in-berlin.de>
Stefan Richter wrote:
> Bill Davidsen wrote:
>
>>> http://kernelnewbies.org/LinuxChanges
>>>
>>>
>> It seems redundant to have the table of contents include links which point back
>> to the line containing the link. Ex: Clicking on the "3 network" link in "8
>> drivers" takes you back to the link with that link, not to the description which
>> you find by scrolling down to the entry you want.
>>
>
> The anchors at the LinuxChanges page are wrong.
> Try http://kernelnewbies.org/Linux_2_6_27 .
>
Thank you, those are indeed correct.
--
Bill Davidsen <davidsen@tmr.com>
"Woe unto the statesman who makes war without a reason that will still
be valid when the war is over..." Otto von Bismark
prev parent reply other threads:[~2008-11-14 17:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 23:59 Linux 2.6.27 Linus Torvalds
2008-10-11 21:03 ` Linux 2.6.27 will be a longtime supported kernel Adrian Bunk
2008-10-12 4:02 ` [stable] " Greg KH
2008-10-12 4:10 ` Adrian Bunk
2008-10-12 7:00 ` Willy Tarreau
2008-10-13 11:27 ` Américo Wang
2008-10-13 12:37 ` Adrian Bunk
2008-10-14 20:10 ` Lennart Sorensen
2008-10-14 21:04 ` [stable] " Greg KH
2008-10-14 22:43 ` Yinghai Lu
2008-10-14 22:48 ` Jiri Kosina
2008-10-14 23:23 ` Greg KH
2008-10-14 23:03 ` Chris Friesen
2008-10-15 2:27 ` Greg KH
2008-10-13 12:42 ` Alex Howells
2008-10-13 12:58 ` Nick Piggin
2008-10-14 17:12 ` Chris Friesen
2008-11-13 22:46 ` Linux 2.6.27 Bill Davidsen
2008-11-14 15:30 ` Stefan Richter
2008-11-14 17:56 ` Bill Davidsen [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=491DBBDA.6040105@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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