From: Jim Paris <jim@jtan.com>
To: Gerald Champagne <gerald.champagne@esstech.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: How can I determine which files are used?
Date: Thu, 13 Sep 2001 17:53:24 -0400 [thread overview]
Message-ID: <20010913175324.A4728@neurosis.mit.edu> (raw)
In-Reply-To: <20010913175007.A4641@neurosis.mit.edu>; from jim@jtan.com on Thu, Sep 13, 2001 at 05:50:07PM -0400
> make clean
> find . | xargs touch -t 198001010101
> make
> find . -not atime -1 | xargs rm $i
>
> Which would set all of the access times to be really old,
> rebuild everything, and then remove all files which weren't
> touched during the build.
Slight correction: make that last command
find . -not -atime -1 | xargs rm $i
and the last sentence "which weren't accessed during the build".
Still untested though :)
-jim
next prev parent reply other threads:[~2001-09-13 21:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-13 21:43 How can I determine which files are used? Gerald Champagne
2001-09-13 21:50 ` Jim Paris
2001-09-13 21:53 ` Jim Paris [this message]
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=20010913175324.A4728@neurosis.mit.edu \
--to=jim@jtan.com \
--cc=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.