Re: GDPR compliance best practices?

From: Peter Backes <rtc@helen.plasma.xg8.de>
Date: Jun 4, 2018, 18:22 UTC
Message-ID: <20180604182212.GA25492@helen.PLASMA.Xg8.DE>
In-Reply-To: <20180604134718.GA7198@thunk.org>

On Mon, Jun 04, 2018 at 09:47:18AM -0400, Theodore Y. Ts'o wrote:

> For people who are doing real work on git repos, other commands that
> we very much care about include "git log --author=<authorname>", "git
> tag --contains", "git blame", etc.

I do not see how those, or anything but git clone (and even that only if author verification is requested) could possibly be affected in any significant way.

Best wishes Peter

-- 
Peter Backes, rtc@helen.PLASMA.Xg8.DE

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.