From: Axel Siebenwirth <axel@pearbough.net>
To: linux-kernel@vger.kernel.org
Subject: Keeping the overview
Date: Mon, 21 Apr 2003 16:16:43 +0200 [thread overview]
Message-ID: <20030421141643.GA1054@neon.pearbough.net> (raw)
Hi,
i was just wondering what all you kernel developers do to keep an overview
over this mass of source code.
Are there any special tools or development GUIs for the kernel?
Best regards,
Axel Siebenwirth
P.S. Please cc me. I am not on the list.
next reply other threads:[~2003-04-21 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-21 14:16 Axel Siebenwirth [this message]
2003-04-21 14:28 ` Jan-Benedict Glaw
2003-04-23 7:29 ` Alex Riesen
2003-04-23 7:54 ` Jan-Benedict Glaw
2003-05-07 10:01 ` Guido Guenther
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=20030421141643.GA1054@neon.pearbough.net \
--to=axel@pearbough.net \
--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
all inboxes | Powered by JetHome®