From: Jim Nelson <james4765@verizon.net>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation/kernel-docs.txt update
Date: Tue, 14 Dec 2004 17:02:59 -0500 [thread overview]
Message-ID: <41BF6313.7040207@verizon.net> (raw)
In-Reply-To: <41BE14FD.20008@osdl.org>
Randy.Dunlap wrote:
> Jim Nelson wrote:
>
>> Apologies for the gzip'ed attachment - many spamfilters don't like all
>> the URL's in this file.
>>
>> The large number of changes are the result of the site author's
>> suggestion of using `lynx -dump
>> http://www.dit.upm.es/~jmseyas/linux/kernel/hackers-docs.html` as the
>> file source.
>
>
> The URL updates and other corrections are good, of course,
> but changing the right margin from approx. 70 to sometimes
> near 80 is not good IMO and should not be done.
>
Right. It was originally formatted with a 74 character margin. I will post a
re-worked patch forthwith.
Jim
next prev parent reply other threads:[~2004-12-14 22:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 22:14 [PATCH] Documentation/kernel-docs.txt update Jim Nelson
2004-12-13 22:17 ` Randy.Dunlap
2004-12-14 22:02 ` Jim Nelson [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-14 22:05 Jim Nelson
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=41BF6313.7040207@verizon.net \
--to=james4765@verizon.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).