From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Miguel Angel Flores <maf@sombragris.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel development environment
Date: Sat, 4 Dec 2004 18:56:11 +0100 [thread overview]
Message-ID: <20041204175611.GS16958@lug-owl.de> (raw)
In-Reply-To: <41B1F97A.80803@sombragris.com>
[-- Attachment #1: Type: text/plain, Size: 714 bytes --]
On Sat, 2004-12-04 18:52:58 +0100, Miguel Angel Flores <maf@sombragris.com>
wrote in message <41B1F97A.80803@sombragris.com>:
> and gcc. My question is: ¿What kind of tools use you, the kernel gurus, to
> write and debug code? ¿It's enough with vi and gcc?
A compiler and a text editor is all you need, your combination is a
perfectly well working combination.
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-12-04 17:56 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 [this message]
2004-12-04 20:21 ` Alessandro Amici
2004-12-04 20:52 ` Miguel Angel Flores
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=20041204175611.GS16958@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-kernel@vger.kernel.org \
--cc=maf@sombragris.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.