git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: demerphq <demerphq@gmail.com>
To: rsbecker@nexbridge.com
Cc: Junio C Hamano <gitster@pobox.com>,
	"brian m. carlson" <sandals@crustytoothpaste.net>,
	Dinesh Dharmawardena <dinesh_dh@outlook.com>,
	git@vger.kernel.org
Subject: Re: Let us not call it git blame
Date: Fri, 3 Mar 2023 09:55:31 +0100	[thread overview]
Message-ID: <CANgJU+Vhh091E+n8B6WaMKh6K2kAG29a2M8Oqm-Zvrr8kRrTRw@mail.gmail.com> (raw)
In-Reply-To: <003201d94d64$1e732030$5b596090$@nexbridge.com>

On Fri, 3 Mar 2023 at 02:24, <rsbecker@nexbridge.com> wrote:
> the core.user and core.email are associated with a nameless single sign on (SSO), or tokenized user, in order to be compliant from a regulatory standpoint. This includes GDPR in Europe and the Privacy Act in Canada. In these cases, there is no identifying information in the commit itself, but externally in the organization's HR and IT departments where identifying information is tightly controlled.

I wish git would make this a core feature.  I think it is one of the
few oversights in the core design of git that there isn't a built
indirection on author and committer data.  It should be possible to
"forget" an author or committer without having to rewrite the repo.
IMO, one day in the future this design deficiency will cause some very
expensive remedial work in the git space, and IMO it is only a
question of when, but sods law says it will be at some very
inconvenient time.

It really should be technically simple to remedy as well, replacing
author and committer data with a hash or ID which is used to indirect
into a file of author information that is *not* version controlled
would essentially solve it.  If someone wanted to change their name
they would update the file, if they wanted to be forgotten they could
simply delete that line from the file and push it.  While not a 100%
complete solution it would go a LONG way to address most people's
privacy concerns and other practical identity management concerns (eg,
"my email changed"). The .mailmap support is just a bandaid, it
doesn't actually address the core problem and in fact in some ways it
makes it worse. If git provided support for hooking the id lookups
then queries to resolve the ID or names could be made to a third party
software or service, like an open source service for the public, or an
internal service owned by HR in the corporate context. It isn't rocket
science, it just requires recognition that names are not static
identifiers.

cheers,
Yves

  reply	other threads:[~2023-03-03  8:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <SY6P282MB3782FD975E6F39951C5A43DA92B29@SY6P282MB3782.AUSP282.PROD.OUTLOOK.COM>
2023-03-02 22:00 ` Let us not call it git blame Dinesh Dharmawardena
2023-03-02 22:16   ` brian m. carlson
2023-03-02 23:47     ` Junio C Hamano
2023-03-03  0:07       ` rsbecker
2023-03-03  8:55         ` demerphq [this message]
2023-03-03  1:31       ` brian m. carlson
2023-03-03  8:28   ` demerphq
2023-03-03 18:28   ` Peter Hadlaw
2023-03-07 12:08   ` Ævar Arnfjörð Bjarmason
2023-03-09 20:28   ` Elijah Lynn

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: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CANgJU+Vhh091E+n8B6WaMKh6K2kAG29a2M8Oqm-Zvrr8kRrTRw@mail.gmail.com \
    --to=demerphq@gmail.com \
    --cc=dinesh_dh@outlook.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=rsbecker@nexbridge.com \
    --cc=sandals@crustytoothpaste.net \
    /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/mirrors/git.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).