On 6/25/08, Jakub Narebski <jnareb@xxxxxxxxx> wrote: > On Wed, 25 Jun 2008, Avery Pennarun wrote: > > Now the catch is, if I want to implement the daemon I was talking > > about earlier, I'd like to be able to notice untracked files (or > > directories with untracked files) individually. Ideally, I guess the > > best way would be to just keep a separate list of all existing files > > that aren't in the index, and have git status look at that rather than > > at the actual filesystem. > > > > Are there any suggestions for how best to do this? > > You can try to take a look at how (third-party and Linux only) inotify > extension for Mercurial works. AFAIK IIRC it uses some kind of daemon > which watches for inotify notices and updates Mercorial's equivalent > of index. Sorry, I asked the wrong question. I wasn't asking how to implement the daemon, which I think I can do without much trouble. I actually need to know how to represent the information. I was thinking of handling updated files by doing update-index --no-assume-unchanged on files that change. But where should I store information about *untracked* files that have changed, so that git-status can still report them but not have to scan them all? Thanks, Avery -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
