Mark J. Nelson wrote:
> 
>>>> 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.

I think (I haven't properly test) that having an .hgignore file helps in 
workspaces that have been built in.

My .hgignore file is usually just this:

closed/*
archives/*
packages/*
proto/*
webrev/*
log/*
*.o

This stops things like 'hg status' wandering down into the proto areas.
The reason I have closed in there is because this is a completely open 
repo without the usr/closed source code.  It also means that it ignores 
(a lot but not all) built object code.


--
Darren J Moffat

Reply via email to