Re: GDPR compliance best practices?

From: Johannes Sixt <j6t@kdbg.org>
Date: Jun 8, 2018, 22:09 UTC
Message-ID: <bb9d72e4-cae1-74f6-60b7-f12d46fddb1d@kdbg.org>
In-Reply-To: <20180608025313.GA12749@thunk.org>

Am 08.06.2018 um 04:53 schrieb Theodore Y. Ts'o:

> And of course, that's the other thing you seem to fundamentally not
> understand about how git works.  Every developer in the world working
> on that open source project has their own copy.

Everyone here understands how Git works, of course.

"*shrug* but that's how Git works" does *NOT* override the GDPR.

-- Hannes

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