From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Alex Riesen" <raa.lkml@gmail.com>
Cc: "Junio C Hamano" <junkio@cox.net>, git@vger.kernel.org
Subject: Re: cygwin, 44k files: how to commit only index?
Date: Fri, 8 Dec 2006 15:16:41 +0100 [thread overview]
Message-ID: <81b0412b0612080616t3d43f739gc201879fddcc20a3@mail.gmail.com> (raw)
In-Reply-To: <20061207221503.GA4990@steel.home>
On 12/7/06, Alex Riesen <fork0@t-online.de> wrote:
> > Maybe you want "assume unchanged"?
>
> If that is core.ignoreState you mean, than maybe this is what I mean.
> I haven't tried it yet (now I wonder myself why I haven't tried it).
> But (I'm repeating myself, in
> <81b0412b0612060235l5d5f93d0hd1aaf34924f7783@mail.gmail.com>)
> I do not really understand how it _can_ help: "I ask because it does
> not ignore stat info, as the name implies. Because if it would,
> there'd be no point of calling lstat at all, wouldn't it?" That last
> question was about refresh_cache_entry - it calls lstat
> unconditionally.
>
> Still, I guess I'll have to try it.
>
Tried. No noticeable difference:
$ git repo-config core.ignorestat true; time gup --refresh
real 0m8.004s
user 0m1.936s
sys 0m5.702s
$ git repo-config core.ignorestat false; time gup --refresh
real 0m7.787s
user 0m1.890s
sys 0m5.703s
$
prev parent reply other threads:[~2006-12-08 14:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 14:27 cygwin, 44k files: how to commit only index? Alex Riesen
2006-12-07 19:16 ` Junio C Hamano
2006-12-07 19:26 ` Shawn Pearce
2006-12-07 19:35 ` Shawn Pearce
2006-12-07 21:26 ` Christian MICHON
2006-12-09 8:27 ` Torgil Svensson
2006-12-07 19:57 ` Junio C Hamano
2006-12-07 20:29 ` Shawn Pearce
2006-12-07 21:53 ` Junio C Hamano
2006-12-07 22:15 ` Alex Riesen
2006-12-07 22:29 ` Junio C Hamano
2006-12-08 5:27 ` Alex Riesen
2006-12-08 6:54 ` Junio C Hamano
2006-12-08 7:27 ` Alex Riesen
2006-12-08 7:36 ` Junio C Hamano
2006-12-08 7:48 ` Alex Riesen
2006-12-08 8:43 ` Alex Riesen
2006-12-08 14:16 ` Alex Riesen [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=81b0412b0612080616t3d43f739gc201879fddcc20a3@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).