Re: What's cooking in git.git (May 2015, #04; Mon, 11)
- From
- Trevor Saunders <tbsaunde@tbsaunde.org>
- Date
- May 12, 2015, 02:13 UTC
- Message-ID
- <20150512021346.GF18112@tsaunders-iceball.corp.tor1.mozilla.com>
- In-Reply-To
- <xmqqk2we20mu.fsf@gitster.dls.corp.google.com>
On Mon, May 11, 2015 at 03:46:33PM -0700, Junio C Hamano wrote:
Show 27 quoted lines
> * nd/untracked-cache (2015-03-12) 24 commits
> - git-status.txt: advertisement for untracked cache
> - untracked cache: guard and disable on system changes
> - mingw32: add uname()
> - t7063: tests for untracked cache
> - update-index: test the system before enabling untracked cache
> - update-index: manually enable or disable untracked cache
> - status: enable untracked cache
> - untracked-cache: temporarily disable with $GIT_DISABLE_UNTRACKED_CACHE
> - untracked cache: mark index dirty if untracked cache is updated
> - untracked cache: print stats with $GIT_TRACE_UNTRACKED_STATS
> - untracked cache: avoid racy timestamps
> - read-cache.c: split racy stat test to a separate function
> - untracked cache: invalidate at index addition or removal
> - untracked cache: load from UNTR index extension
> - untracked cache: save to an index extension
> - ewah: add convenient wrapper ewah_serialize_strbuf()
> - untracked cache: don't open non-existent .gitignore
> - untracked cache: mark what dirs should be recursed/saved
> - untracked cache: record/validate dir mtime and reuse cached output
> - untracked cache: make a wrapper around {open,read,close}dir()
> - untracked cache: invalidate dirs recursively if .gitignore changes
> - untracked cache: initial untracked cache validation
> - untracked cache: record .gitignore information and dir hierarchy
> - dir.c: optionally compute sha-1 of a .gitignore file
>
> Need extra sets of eyes to review this.I can't usefully comment on the code. However it makes it more pleasent to deal with several big repos I use regularly, and I haven't noticed any bugs yet.
Trev