From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.1 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id B8EEF1F597; Thu, 19 Jul 2018 21:12:16 +0000 (UTC) Date: Thu, 19 Jul 2018 21:12:16 +0000 From: Eric Wong To: "Eric W. Biederman" Cc: meta@public-inbox.org Subject: Re: Searching via git grep? Message-ID: <20180719211216.GA1984@dcvr> References: <87in5bdkbv.fsf@xmission.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87in5bdkbv.fsf@xmission.com> List-Id: "Eric W. Biederman" 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 HEAD' > For v2 it is 'git --rev-list --all | xargs git grep ' > > 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.