user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: handling GDPR requests
Date: Tue, 2 Apr 2019 18:32:27 -0400	[thread overview]
Message-ID: <20190402223227.GC1204@chatter.qube.local> (raw)
In-Reply-To: <20190401175551.naauxlsxpvqyysu5@dcvr>

On Mon, Apr 01, 2019 at 05:55:51PM +0000, Eric Wong wrote:
>> 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.

Thanks, Eric!

I'm not acting on it yet, since the proper process needs to be followed 
via LF legal. Notably, this person's name and email address ended up 
making its way into actual git commits (via "Reported-By:"), so at this 
point I'm mostly sitting back with a large bucket of pop-corn.

-K

  reply	other threads:[~2019-04-02 22:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-01 15:50 handling GDPR requests Konstantin Ryabitsev
2019-04-01 17:55 ` Eric Wong
2019-04-02 22:32   ` Konstantin Ryabitsev [this message]
2019-04-03 20:55   ` Konstantin Ryabitsev
2019-04-03 21:21     ` Eric Wong

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=20190402223227.GC1204@chatter.qube.local \
    --to=konstantin@linuxfoundation.org \
    --cc=e@80x24.org \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

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).