linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rob Wilkens <robw@optonline.net>
To: Mel Gorman <mel@csn.ul.ie>
Cc: Marcus Alanen <marcus@infa.abo.fi>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: Linux VM Documentation - Draft 1
Date: Sun, 12 Jan 2003 12:54:53 -0500	[thread overview]
Message-ID: <1042394092.3162.16.camel@RobsPC.RobertWilkens.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0301121532160.24444-100000@skynet>

On Sun, 2003-01-12 at 10:36, Mel Gorman wrote:
> I wasn't sure how suitable patches would be for documentation but I'll try
> anything once. A tar ball of the current tex source is at
> http://www.csn.ul.ie/~mel/projects/vm/guide/vm_book.tar.gz . There is a
> CVS tree but it's on a computer thats already heavily loaded so I don't
> want to have it hammered.
> 
> The tex sources are in tex/understand and tex/code . To create a DVI,
> simply ./make dvi . If you add "understand" or "code", it'll just generate
> that book.

Not worthy of re-releasing but one small "patch" is page 16 of the pdf
(labelled as page 9 on the top) which reads:
	"the init code is quiet architecture dependent"
but should probably read
	"the init code is quite architecture dependent"
It's a small thing, but whenever I read a technical document and see
small errors like that, it distracts me from the main point of the
article and makes concentrating on the original document harder.

I don't know how to code in tex (maybe one of these years I should
learn), otherwise I'd offer a tex patch for you to apply.  

I'm sure I'm not the first to catch that error, given the number of
people who are probably interested in the article you wrote, it's quite
a document.  It was also very nice of you to share it with the world
gratis.

-Rob

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

  reply	other threads:[~2003-01-12 17:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-12  2:11 Mel Gorman
2003-01-12  2:49 ` Willy Tarreau
2003-01-12 15:11 ` Marcus Alanen
2003-01-12 15:36   ` Mel Gorman
2003-01-12 17:54     ` Rob Wilkens [this message]
2003-01-12 18:06       ` Mel Gorman
2003-01-12 18:03     ` andrea.glorioso
2003-01-12 18:14       ` Mel Gorman
2003-01-13  5:18 ` Linux VM Documentation - Draft 2 Mel Gorman
2003-01-14  1:53   ` Mel Gorman

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=1042394092.3162.16.camel@RobsPC.RobertWilkens.com \
    --to=robw@optonline.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=marcus@infa.abo.fi \
    --cc=mel@csn.ul.ie \
    /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