On Thu, Jul 25, 2013 at 06:28:50PM -0700, Junio C Hamano wrote:
> Ondřej Bílka <nel...@seznam.cz> 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 next; git checkout
This is separate issue as you would need to change index anyway, number
of changes would be proportionate to size of diff so you would not gain
much. Possible problem here is that you would end changing many files.
A possible solution is do rebuilding in background.
For switching often to different branches that are vastly different a
best solution for me seems to keep separate index for each branch.
Also data structure is trigraph: list of files with counts.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html