From: Shawn O. Pearce Date: Mon, 19 Jan 2009 18:11:58 GMT Subject: Re: [PATCH] bash: offer to show (un)staged changes Message-ID: <20090119181158.GH14053@spearce.org> In-Reply-To: <46a038f90901191000i250326e7k2184c149b70fcc8d@mail.gmail.com> Martin Langhoff wrote: > On Mon, Jan 19, 2009 at 12:29 PM, Shawn O. Pearce wrote: > > ... If we had > > an inotify sort of daemon to keep the data current so the prompt > > doesn't have to stat every source file on every display it would > > be reasonable, but we don't have such a thing yet for Git. > > Note that inotify is not recursive and is a hog if you ask it to > monitor lots of dents. > > I am not convinced that an inotify-enabled git is a good idea for > anything but small/mid-sized project. And such don't need it either. > > In other words, the kernel's cache will outperform any userland > attempting to keep track of the fs via inotify. *sigh* I was hoping it would work well for the really huge repository case, like WebKit, where the stats against the work tree just kill the user space application. But if its only good for smaller sets of files, then yea, just doing the stats on demand is going to be better than anything an inotify daemon might be able to offer. -- Shawn.