From: Pavel Roskin <proski@gnu.org>
To: git <git@vger.kernel.org>
Subject: Caching directories
Date: Mon, 23 Jan 2006 23:20:23 -0500 [thread overview]
Message-ID: <1138076423.15105.36.camel@dv> (raw)
Hello!
I'm thinking of moving cg-clean functionality to git. After having
switched to StGIT, it's the last cogito command I'm still using. I
think git can go it much better, since it's a recursive command
traversing the whole repository.
To be safe and useful, the new command should distinguish between
tracked and untracked directories. Untracked files in tracked
directories are usually the first target for cleaning, as they are
mostly automatic backups and temporary files. Untracked directories are
more likely candidates to be preserved, as they can hold external
sources, build output, extensive test data etc.
cg-clean considers a directory untracked if it has no cached files in
it. This carries a significant speed penalty, even if not coded in
bash.
Maybe it's time to start caching directories in git? I mean,
directories corresponding to tree objects could have their stats
recorded in the cache. This would allow to distinguish between tracked
and untracked directories without scanning them recursively.
--
Regards,
Pavel Roskin
next reply other threads:[~2006-01-24 4:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 4:20 Pavel Roskin [this message]
2006-01-25 5:52 ` Caching directories Junio C Hamano
2006-01-25 7:29 ` Pavel Roskin
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=1138076423.15105.36.camel@dv \
--to=proski@gnu.org \
--cc=git@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;
as well as URLs for NNTP newsgroup(s).