kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: rpjday@crashcourse.ca (Robert P. J. Day)
To: kernelnewbies@lists.kernelnewbies.org
Subject: The Kernel Newbies Crash Course LKD4 Challenge! Play along at home!
Date: Tue, 23 Sep 2014 03:47:40 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1409230340370.9431@localhost> (raw)
In-Reply-To: <20140922185527.6477bb35@BR9TG4T3.de.ibm.com>

On Mon, 22 Sep 2014, Dominik Dingel wrote:

> On Sat, 20 Sep 2014 09:24:40 -0400 (EDT)
> "Robert P. J. Day" <rpjday@crashcourse.ca> wrote:
>
> >
> >   Questions?
>
> As the book is IIUC publicly available would it be possible to set
> up a GIT repository with the content and everyone could mark or
> change the pages by e.g. special latex commands and sent you a
> respective patch?
>
> This way it would be easier to see what is already reviewed and does
> not need to change, and there might be even the small chance that
> people could include the requesting change, instead of only putting
> a marker where the change should happen.
>
> The work you have to do should hopefully stays the same, as it would
> be with emails you get?

  i'm not aware that LKD3 is publicly available -- i know LDD3 is. and
in any event, as someone who has edited/pre-pub reviewed *many*
technical books, i can assure you that authors don't want updates
recorded that way, they much prefer bullet points labelled with page
and paragraph number so *they* can decide how that content should be
rewritten.

  i/we are not trying to rewrite the book -- all i'm trying to do is
keep track of what needs updating so that, if there *is* an LKD4, the
author has a concise list of changes. the goal here is to make life
easy for the author, not so much for the rest of us.

  anyway, i just need to finish up a couple things and i can start
adding in some updates people have already sent me.

rday

p.s. i know i mentioned this earlier, but in addition to simple
updates:

 http://www.crashcourse.ca/wiki/index.php/Updates_to_LKD3

feel free to suggest improvements to explanations, entirely new
features/subsystems that should be addressed, and so on. whatever
occurs to you, and i'll try to get it onto that page somewhere.

  note that section 5 on that page is the chapter by chapter listing,
so section 5.1 corresponds to chapter 1, and so on.

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

      reply	other threads:[~2014-09-23  7:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-20 13:24 The Kernel Newbies Crash Course LKD4 Challenge! Play along at home! Robert P. J. Day
2014-09-20 19:59 ` Gustavo Silva
2014-09-20 20:05   ` Gustavo Silva
2014-09-20 20:12   ` Robert P. J. Day
2014-09-20 20:24     ` Gustavo Silva
2014-09-22 16:55 ` Dominik Dingel
2014-09-23  7:47   ` Robert P. J. Day [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=alpine.LFD.2.11.1409230340370.9431@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=kernelnewbies@lists.kernelnewbies.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).