From: Diego Calleja <diegocg@gmail.com>
To: Ian McDonald <imcdnzl@gmail.com>
Cc: greg@kroah.com, shemminger@osdl.org, netdev@vger.kernel.org,
linux-net@vger.kernel.org, linux-kernel@vger.kernel.org,
riel@surriel.com
Subject: Re: [ANNOUNCE] linux-net wiki
Date: Fri, 7 Oct 2005 10:15:38 +0200 [thread overview]
Message-ID: <20051007101538.7778bd1a.diegocg@gmail.com> (raw)
In-Reply-To: <cbec11ac0510061834j53678e7cq@mail.gmail.com>
El Fri, 7 Oct 2005 14:34:10 +1300,
Ian McDonald <imcdnzl@gmail.com> escribió:
> >
> > Why not just work with the existing kernelnewbies wiki:
> > http://wiki.kernelnewbies.org
> > instead of creating another site?
> >
> Having a quick look around and looking at the name in particular I
> think they are different target audiences...
The fact that it's called "kernelnewbies" doesn't meant it's targetted only
to non-expert people - everybody, including me, you, Linus and all the "core"
kernel hackers are "newbies" WRT to some parts of the kernel. The one thing
that can keep someone being a newbie forever is considering himself an
"expert". In fact you can find some linux kernel "gurus" there...
Also, kernelnewbies is not linux-specific either so there's a chance that even
gurus could learn something interesting (and teach something to others).
Or at least that has always been the intention of the kernelnewbies project.
(That doesn't mean I'm against the linux-net wiki, I just wanted to point out
that kernelnewbies isn't just for "newbies" ;)
next prev parent reply other threads:[~2005-10-07 8:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-06 21:00 [ANNOUNCE] linux-net wiki Stephen Hemminger
2005-10-06 20:29 ` Jeff V. Merkey
2005-10-07 1:24 ` Greg KH
2005-10-07 1:34 ` Ian McDonald
2005-10-07 8:15 ` Diego Calleja [this message]
2005-10-07 4:45 ` Stephen Hemminger
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=20051007101538.7778bd1a.diegocg@gmail.com \
--to=diegocg@gmail.com \
--cc=greg@kroah.com \
--cc=imcdnzl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=riel@surriel.com \
--cc=shemminger@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).