From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@80x24.org>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN:  
X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00
	shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2
Received: from localhost (dcvr.yhbt.net [127.0.0.1])
	by dcvr.yhbt.net (Postfix) with ESMTP id 5A75D1F463;
	Mon, 30 Sep 2019 20:33:04 +0000 (UTC)
Date: Mon, 30 Sep 2019 20:33:04 +0000
From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: meta@public-inbox.org
Subject: Re: [PATCH] wwwtext: support $INBOX_URL/_/text/config/raw
Message-ID: <20190930203304.GA2981@dcvr>
References: <20190927104825.28270-1-e@80x24.org>
 <20190930174421.GB6124@chatter.i7.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20190930174421.GB6124@chatter.i7.local>
List-Id: <meta.public-inbox.org>

Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> On Fri, Sep 27, 2019 at 10:48:25AM +0000, Eric Wong wrote:
> > This returns a git-config(1)-compatible file to make it easier
> > to get started on mirroring an existing public-inbox.  Omitting
> > the "raw" from the URL works, as well, but I'm not sure if
> > it's very useful.
> 
> This is now live on lore.kernel.org. Theoretically, this provides everything
> needed to recreate mirrors via grokmirror, once the post-update hook is
> changed to incorporate this feature.

Cool!  I'm starting to form a better idea of client-side stuff I want
to do...

> Quick question that occurred to me -- when there are history-rewriting
> changes on the master mirror (GDPR-related message removals, etc), how well
> will that propagate to other mirrors? Would they need to be fully reindexed?

public-inbox-index should pick up changes and only reindex the
history starting with the rewrite.  t/v2mirror.t tests the purge
case, but purge is a special case of replace (which edit uses).