From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 11FFB202BB; Mon, 1 Apr 2019 17:55:52 +0000 (UTC) Date: Mon, 1 Apr 2019 17:55:51 +0000 From: Eric Wong To: Konstantin Ryabitsev Cc: meta@public-inbox.org Subject: Re: handling GDPR requests Message-ID: <20190401175551.naauxlsxpvqyysu5@dcvr> References: <20190401155032.GB3701@chatter.qube.local> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20190401155032.GB3701@chatter.qube.local> List-Id: Konstantin Ryabitsev wrote: > Hello: > > Well, I have my first GDPR request. What's the recommended mechanism of > dealing with that? The message in question dates back to mid-last year and I > see two problems with deleting it from the repository: > > 1. It's in the previous epoch repo of LKML > 2. Deleting/editing that message would require a massive repo rebase with > associated db reindexing. I'm not sure I want to think about how long that > would take. Try the -purge tool: https://public-inbox.org/meta/20190111041008.24361-8-e@80x24.org/ I haven't used it outside of tests, so try it in a throwaway repo, first :) It doesn't need to do a full reindex. And the "rebase" should be quick when done via fast-import (doesn't need to rewrite blobs, only commit history). The repack might be the slowest part of the operation.