On Thu, Jul 25, 2013 at 06:28:50PM -0700, Junio C Hamano wrote:
> Ondřej Bílka writes:
>
> > If grepping random commit in history is important use case then keeping
> > db information in history makes sense. Otherwise just having database
> > for current version and updating it on the fly as vers
Ondřej Bílka writes:
> If grepping random commit in history is important use case then keeping
> db information in history makes sense. Otherwise just having database
> for current version and updating it on the fly as version changes is
> enough.
Will you reindex every time I do "git checkout n
On Thu, Jul 25, 2013 at 01:41:13PM -0700, Junio C Hamano wrote:
> Ondřej Bílka writes:
>
> > One solution would be to use same trick as was done in google code.
> > Build and keep database of trigraphs and which files contain how many of
> > them. When querry is made then check
> > only these fi
Ondřej Bílka writes:
> One solution would be to use same trick as was done in google code.
> Build and keep database of trigraphs and which files contain how many of
> them. When querry is made then check
> only these files that have appropriate combination of trigraphs.
This depends on how you
On Thu, Jul 25, 2013 at 08:29:05PM +0200, Ondřej Bílka wrote:
> One solution would be to use same trick as was done in google code.
> Build and keep database of trigraphs and which files contain how many of
> them. When querry is made then check
> only these files that have appropriate combination
Hi,
When I do git grep then with big codebase (gcc) it executes slowly.
I am thinking to add option to speed up search time.
One solution would be to use same trick as was done in google code.
Build and keep database of trigraphs and which files contain how many of
them. When querry is made the
6 matches
Mail list logo
