public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Warne <nick@linicks.net>
To: Yitzchak Eidus <ieidus@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: question about code from the linux kernel development ( se )  book
Date: Fri, 21 Oct 2005 15:00:27 +0100	[thread overview]
Message-ID: <200510211500.28100.nick@linicks.net> (raw)

Steven Rostedt wrote:

>> ( thnks for the help , please if it can be done answer quickly i am
>> tanker in the idf and need to come back to the army soon , ( no
>> internet there... ) )
> 
> BTW, this is not an IRC, we use normal capitalization and normal spelling
> (when we know how to spell a word ;-).  So the next time you send to the
> list, send it as if you were writing a serious letter, or you may just be
> ignored. (as you might have been if I didn't respond).

Well, I am a real newbie to Linux coding, but I think the guy tried to do 
right (irc sent him here) - maybe I am not used to the terseness of Kernel 
hackers in their replies sometimes.


Yitzchak: I have the book - by Robert Love.  I see the same code (page 53), 
but, alas I haven't a clue...

My advice is drop a mail to Robert about it - he _is_ the author, and I am 
sure he will answer your query.

Nick
-- 
http://sourceforge.net/projects/quake2plus

"Person who say it cannot be done should not interrupt person doing it."
-Chinese Proverb


             reply	other threads:[~2005-10-21 14:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-21 14:00 Nick Warne [this message]
2005-10-21 15:56 ` question about code from the linux kernel development ( se ) book Steven Rostedt
  -- strict thread matches above, loose matches on Subject: below --
2005-10-21 11:22 Yitzchak Eidus
2005-10-21 13:03 ` Steven Rostedt
2005-10-21 13:10   ` Jesper Juhl
2005-10-21 14:41   ` Yitzchak Eidus
2005-10-21 15:07     ` Steven Rostedt
2005-10-21 18:36   ` Lee Revell

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=200510211500.28100.nick@linicks.net \
    --to=nick@linicks.net \
    --cc=ieidus@gmail.com \
    --cc=linux-kernel@vger.kernel.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