From: "Ondřej Bílka" <neleai@seznam.cz>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC] Faster git grep.
Date: Fri, 26 Jul 2013 07:45:50 +0200 [thread overview]
Message-ID: <20130726054550.GA23320@domone.kolej.mff.cuni.cz> (raw)
In-Reply-To: <7vhafi3y99.fsf@alter.siamese.dyndns.org>
On Thu, Jul 25, 2013 at 06:28:50PM -0700, Junio C Hamano wrote:
> Ondřej Bílka <neleai@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
> master"?
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.
prev parent reply other threads:[~2013-07-26 5:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 18:29 [RFC] Faster git grep Ondřej Bílka
2013-07-25 20:08 ` Jeff King
2013-07-25 20:41 ` Junio C Hamano
2013-07-25 21:31 ` Ondřej Bílka
2013-07-26 1:28 ` Junio C Hamano
2013-07-26 5:45 ` Ondřej Bílka [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130726054550.GA23320@domone.kolej.mff.cuni.cz \
--to=neleai@seznam.cz \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).