>>> It's still impressive that we can burn alsost 12 seconds of CPU time >>> to find one character difference in my workspace :-(
Really? How long does it take "wx init" to check your entire workspace and find that same change? Presumably your development habits aren't changing dramatically, and you know either exactly which files you've modified, or can come close (within a level or two in the source tree, and identify the directories.) "hg status" accepts file and directory arguments, and using them will dramatically reduce the search time. (For example, much of my work prior to tools putback involved "hg status usr/src/tools" to get everything I had touched.) Mostly, the only time you should be incurring full-workspace searches are for an "hg commit" which follows an "hg merge," because then a partial commit is not allowed. --Mark >> if anyone wanted to do something about this, they could port this: >> >> http://www.selenic.com/mercurial/wiki/index.cgi/InotifyExtension >> >> from linux inotify to the solaris file event monitor interface... > > Couldn't we also have an opt-in 'hg update' like 'wx update' that kept a > cache of changed files? It would be possible for the user to edit files > and forget about them, but we could have anything that pushed data to > the server error out if the cached copy didn't match the real thing. > > - Eric > > -- > Eric Schrock, Fishworks http://blogs.sun.com/eschrock > _______________________________________________ > scm-migration-dev mailing list > scm-migration-dev at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/scm-migration-dev >
