All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerald Champagne <gerald.champagne@esstech.com>
To: linux-mips@oss.sgi.com
Subject: How can I determine which files are used?
Date: Thu, 13 Sep 2001 16:43:19 -0500	[thread overview]
Message-ID: <3BA12877.6030505@esstech.com> (raw)

Is there a recommended method of determining which files in the
Linux source tree are used with a given .config file?  I've already
removed the obvious things like unused entries in the arch directory
and a couple of driver directories, but is there a way to generate a
list of only the files that are used?

I know I've read discussions about someday splitting up the source code
into smaller blocks, but can someone point me towards information on how
to prune the existing source tree?

Thanks.

Gerald

             reply	other threads:[~2001-09-13 21:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-13 21:43 Gerald Champagne [this message]
2001-09-13 21:50 ` How can I determine which files are used? Jim Paris
2001-09-13 21:53   ` Jim Paris
2001-09-14  1:35 ` Keith Owens

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=3BA12877.6030505@esstech.com \
    --to=gerald.champagne@esstech.com \
    --cc=linux-mips@oss.sgi.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.