From: Miguel Angel Flores <maf@sombragris.com>
To: Alessandro Amici <alexamici@fastwebnet.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel development environment
Date: Sat, 04 Dec 2004 21:52:17 +0100 [thread overview]
Message-ID: <41B22381.10008@sombragris.com> (raw)
In-Reply-To: <200412042121.49274.alexamici@fastwebnet.it>
Alessandro Amici wrote:
>At the very minimum you need to add grep to your tool set.
>It will save you a lot of flames :)
>
>
As I can see the kernel hacker tools are the standard GNU tools. I'm in
the correct way ;)
Thank you.
next prev parent reply other threads:[~2004-12-04 20:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-04 17:52 kernel development environment Miguel Angel Flores
2004-12-04 17:56 ` Jan-Benedict Glaw
2004-12-04 20:21 ` Alessandro Amici
2004-12-04 20:52 ` Miguel Angel Flores [this message]
2004-12-04 21:37 ` Alessandro Amici
2004-12-04 21:47 ` Lee Revell
2004-12-04 21:40 ` Michal Schmidt
2004-12-04 22:45 ` Lee Revell
2004-12-04 23:37 ` Randy.Dunlap
2004-12-04 23:55 ` Lee Revell
2004-12-05 0:34 ` Michal Schmidt
2004-12-05 0:39 ` Lee Revell
2004-12-05 21:29 ` Baruch Even
2004-12-05 0:05 ` Jim Nelson
2004-12-16 1:35 ` Bill Davidsen
2004-12-04 21:58 ` Roger Luethi
2004-12-05 17:41 ` Alan Cox
2004-12-05 20:16 ` Herbert Poetzl
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=41B22381.10008@sombragris.com \
--to=maf@sombragris.com \
--cc=alexamici@fastwebnet.it \
--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