From: David Kastrup <dak@gnu.org>
To: git@vger.kernel.org
Subject: Sort of a feature proposal
Date: Wed, 07 May 2008 16:48:17 +0200 [thread overview]
Message-ID: <86fxsutbke.fsf@lola.quinscape.zz> (raw)
Hi, I have some large git repositories on a USB drive (ext3 file
system). That means that when replugging the drive, the recorded st_dev
data in the index is off, meaning that the whole repo directory
structure gets reread as the stat data of all directories has changed.
That's a nuisance. Can't we have some heuristic or configuration option
where we, say, record the st_dev of the _index_ file, and if that has
changed, we propagate that change to the st_dev of its contents? I'd
like to see something that works more efficiently than rescanning the
whole disk every time I hibernate my computer.
Thanks,
--
David Kastrup
next reply other threads:[~2008-05-07 14:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 14:48 David Kastrup [this message]
2008-05-07 15:41 ` Sort of a feature proposal Nicolas Pitre
2008-05-07 16:00 ` Stephen R. van den Berg
2008-05-07 16:03 ` Avery Pennarun
2008-05-07 16:25 ` Linus Torvalds
2008-05-07 17:39 ` David Kastrup
2008-05-07 17:50 ` Dmitry Potapov
2008-05-07 18:05 ` David Kastrup
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=86fxsutbke.fsf@lola.quinscape.zz \
--to=dak@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