From: chambilkethakur@gmail.com (Anuz Pratap Singh Tomar)
To: kernelnewbies@lists.kernelnewbies.org
Subject: surviving in lkml
Date: Thu, 2 Jun 2011 02:25:17 +0100 [thread overview]
Message-ID: <BANLkTi=9NnJt8tGGK_MsF-AXfFMb+nNd2w@mail.gmail.com> (raw)
Hi list,
This is an interesting story/presentation by an lkml regular, not technical
but useful.
https://docs.google.com/viewer?a=v&pid=explorer&chrome=true&srcid=0B8baQh2SFt66N2Q3M2FkMzYtZmRjYi00NTEzLWEwZWYtOTEzMDk5MzhkOTQ1&hl=en_US&pli=1
Regards
Anuz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110602/4408a598/attachment.html
next reply other threads:[~2011-06-02 1:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 1:25 Anuz Pratap Singh Tomar [this message]
2011-06-02 1:51 ` surviving in lkml João Eduardo Luís
2011-06-02 6:57 ` Greg KH
2011-06-02 7:56 ` Stéphan Gorget
2011-06-02 16:34 ` João Eduardo Luís
2011-06-02 16:47 ` Greg Freemyer
2011-06-02 8:13 ` Althaf
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='BANLkTi=9NnJt8tGGK_MsF-AXfFMb+nNd2w@mail.gmail.com' \
--to=chambilkethakur@gmail.com \
--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).