From: Eric Wong <e@80x24.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: meta@public-inbox.org
Subject: Re: Searching via git grep?
Date: Thu, 19 Jul 2018 21:12:16 +0000 [thread overview]
Message-ID: <20180719211216.GA1984@dcvr> (raw)
In-Reply-To: <87in5bdkbv.fsf@xmission.com>
"Eric W. Biederman" <ebiederm@xmission.com> wrote:
> Have you considered searching public inboxes via git grep?
Not yet...
> For a big server lore.kernel.org with a lot of searches and a lot of
> clients it might not make sense. But for home use where searches are
> rare and the indexes can not be kept in ram, but the mailbox might fit
> git grep sounds attractive?
>
> I performed a preliminary test and just running git grep manually and
> I was search all of the git mailling list archive pretty much
> immediately.
>
> For v1 it is just 'git grep <regexp> HEAD'
> For v2 it is 'git --rev-list --all | xargs git grep <regexp>'
>
> If this sounds reasonable to you I will take a look at what it takes to
> wire that up over the next while.
Having something like this on a potentially public-facing web UI
seems like a liability support-wise(*).
However, I'd be open to having this as a command-line tool.
Maybe in the scripts/ directory for one-off scripts...
If I were building a personal mail tool, I could use
scripts/dupe-finder as a starting point.
(*) I would also caution against having personal mail accessible
over http://localhost/ on any port without a password; as
there's attacks on browsers which could hit them.
next prev parent reply other threads:[~2018-07-19 21:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 20:47 Searching via git grep? Eric W. Biederman
2018-07-19 21:12 ` Eric Wong [this message]
2018-07-19 22:27 ` Eric W. Biederman
2018-07-20 6:11 ` Eric Wong
2018-07-20 12:37 ` Eric W. Biederman
2018-07-20 23:56 ` Eric W. Biederman
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180719211216.GA1984@dcvr \
--to=e@80x24.org \
--cc=ebiederm@xmission.com \
--cc=meta@public-inbox.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).