Re: GDPR compliance best practices?

From: Theodore Y. Ts'o <tytso@mit.edu>
Date: Jun 4, 2018, 13:47 UTC
Message-ID: <20180604134718.GA7198@thunk.org>
In-Reply-To: <20180603221616.GA14636@helen.PLASMA.Xg8.DE>

On Mon, Jun 04, 2018 at 12:16:16AM +0200, Peter Backes wrote:

Show 5 quoted lines

> 
> Verifying the commit ID by itself wouldn't be any less efficient than 
> before. Admitteldly, it wouldn't verify the author and authordate 
> integrity anymore without additional work. That would be some overhead, 
> sure, and could be done on demand, and would mostly affect clones.

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.

At least for any repo that *I* control, slow those down, and I wouldn't downgrade my git binary/repo just to make some imperialistic European bureaucrats happy.

Cheers,

					- Ted

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