From: Junio C Hamano <gitster@pobox.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: "Avery Pennarun" <apenwarr@gmail.com>,
"Stephen R. van den Berg" <srb@cuci.nl>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: update-index --assume-unchanged doesn't make things go fast
Date: Fri, 27 Jun 2008 19:03:49 -0700 [thread overview]
Message-ID: <7vd4m2l3i2.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: m3lk0qiy2i.fsf@localhost.localdomain
Jakub Narebski <jnareb@gmail.com> writes:
> By the way, from time to time there on this mailing list is idea
> to add entries for directories in the index. This could help situation
> like yours, tracking emty directories, faster operations when some trees
> are unchanged, subtree <-> subproject changes.
Tracking empty directories might be helped by having an explicit entry in
the index (even though it may not be the only possible implementation). I
however suspect you are overvaluing it for "some trees are unchanged"
case:
$ mkdir -p a/b
$ stat a | grep Modify
Modify: 2008-06-27 11:38:13.000000000 -0700
$ >a/b/c
$ stat a | grep Modify
Modify: 2008-06-27 11:38:13.000000000 -0700
$ >a/d
$ stat a | grep Modify
Modify: 2008-06-27 11:38:32.000000000 -0700
You have to descend into the leaf level anyway and directory mtime does
not allow you to check that much.
prev parent reply other threads:[~2008-06-28 2:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 16:44 update-index --assume-unchanged doesn't make things go fast Avery Pennarun
2008-06-25 17:38 ` Michael J Gruber
2008-06-25 18:02 ` Avery Pennarun
2008-06-26 8:47 ` Michael J Gruber
2008-06-25 19:30 ` Jakub Narebski
2008-06-25 19:41 ` Junio C Hamano
2008-06-25 19:53 ` Avery Pennarun
2008-06-25 21:35 ` Jakub Narebski
2008-06-26 1:30 ` Avery Pennarun
2008-06-26 11:22 ` Stephen R. van den Berg
2008-06-27 17:01 ` Avery Pennarun
2008-06-27 17:31 ` Jakub Narebski
2008-06-27 17:56 ` Avery Pennarun
2008-06-27 18:09 ` Dana How
2008-06-27 18:51 ` Avery Pennarun
2008-06-28 2:03 ` Junio C Hamano [this message]
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=7vd4m2l3i2.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=srb@cuci.nl \
/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).