I'm grepping through a large pile of code managed by git, and whenever I do a grep, I see piles and piles of messages of the form:
> grep pattern * -R -n
whatever/.git/svn: No such file or directory
Is there any way I can make those lines go away?
ag,ack, orcgrepinstead - they're much faster/better thangrepfor searching code repositories.No such file or directorymessages for files and/or directories that exist? Or, conversely, how cangrep *be getting names of files that don't exist? Is this a race condition, where some other process manipulates the directory tree (creating, renaming and deleting files) while thegrepis running?