Thread (7 messages) 7 messages, 6 authors, 2016-08-11

Re: cygwin, 44k files: how to commit only index?

From: Shawn Pearce <hidden>
Date: 2016-08-11 20:15:03

Junio C Hamano [off-list ref] wrote:
"Alex Riesen" [off-list ref] writes:
quoted
I have a kind of awkward project to work with (~44k files, many binaries).

The normal "git commit", which seem to be more than enough
for anything and anyone else, is a really annoying procedure
in my context. It spend too much time refreshing index and
generating list of the files for the commit message.

At first I stopped using git commit -a (doing only update-index),
I am not sure what you are trying.  Do you mean stat() is slow
on your filesystem?
Its Cygwin/NTFS.  lstat() is slow.  readdir() is slow.  I have the
same problem on my Cygwin systems.
 
quoted
Is there any simple way to modify git commit for such a workflow?
Failing that, any simple and _fast_ way to find out if the index
is any different from HEAD? (so that I don't produce empty commits).
Maybe you want "assume unchanged"?
Yes, basically.  The Cygwin/NTFS issues Alex is pointing out are
exactly why git-gui has a "Trust File Modification Timestamp" option
on both a per-repository and global level.  My larger repositories
(~10k files) are difficult to work with without that option enabled.

-- 
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help