git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Emily Shaffer <emilyshaffer@google.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"brian m. carlson" <sandals@crustytoothpaste.net>,
	git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jan 2021, #02; Fri, 8)
Date: Thu, 14 Jan 2021 23:22:34 -0800	[thread overview]
Message-ID: <xmqqft32u0jp.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <YADaJ1gfbxQaLGXf@google.com> (Emily Shaffer's message of "Thu, 14 Jan 2021 15:56:23 -0800")

Emily Shaffer <emilyshaffer@google.com> writes:

> Taking the time to redesign commit format (e.g. use user.id instead of
> user.name/user.email) ...

I have seen that "ID", which doesn't have permanent association to
<name, email>, has been raised as a solution from time to time, but
I am not quite sure what problem is being solved.  At some point,
you'd need to translate the "ID" to a way humans use to refer to
each other---you cannot forever be saying "Ah, commits by this
contributor #70763 is consistently good and seems to know the
history traversal quite well.  We wish who it is so that we can ask
to review what we have been working on."

So we must have a mapping from ID to <name, email> or something.
How is that mapping maintained?  Even though Git is a version
tracking system and the mapping will change over time, we'll only
keep the "latest"?  That may not work very well, as a work for hire
contract a company made with one of the project participants would
have been made with a real person with a name, not just an anonymous
contributor #70763---the work done under the contract would not
become invalid merely because mapping from ID to <name, email>
changes, and those who made contract with a person with a certain
name would want to make sure the contributor #70763 who made the
work is actually who they thought they had contract with.

If we do not keep track of the change of the mapping ourselves, the
ecosystem around us will start doing so to fill the gap, so I do not
think use of "ID" would help you dissociate from your past self,
while keeping the credit for your past commits.

And if the mapping is version controlled in such a way that an "ID"
can be used to look up its name at any given time in the past, it
would not be so different from what we already have.

One advantage I could imagine that "ID" based system may have is
that one who wants to completely dissociate from an older name
and/or email can just start using a totally different "ID" with
totally different name, and pretend that s/he has no relationship
with the old person associated with the old "ID", and nobody would
be able to tell.  But again, I suspect that it can also be done
without "ID".  So...

> ... also gives us room to improve other things we
> don't like about the commit format (e.g. limited to single author).

I personally think having "author" is a mistake, iff some people do
not like "limited to a single author".  You can write everybody's
name in the trailer as "Co-Authored-by:" and at that point you do
not need any author in the commit object header.

But that is so miniscule a feature that I do not think it is worth
making a backward incompatible change to change the number of the
commit object header for the author from 1 to either 0 or many.

Anyway, thanks for an opportunity for a (somewhat) fun thought
experiment.

Goodnight.

  reply	other threads:[~2021-01-15  7:24 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-08 19:22 What's cooking in git.git (Jan 2021, #02; Fri, 8) Junio C Hamano
2021-01-09 10:55 ` Ævar Arnfjörð Bjarmason
2021-01-09 21:28   ` Junio C Hamano
2021-01-09 22:05     ` brian m. carlson
2021-01-09 23:20       ` Junio C Hamano
2021-01-11  1:53         ` brian m. carlson
2021-01-11 19:04           ` Junio C Hamano
2021-01-12 14:00             ` Ævar Arnfjörð Bjarmason
2021-01-14 23:52               ` Emily Shaffer
2021-01-14 23:56                 ` Emily Shaffer
2021-01-15  7:22                   ` Junio C Hamano [this message]
2021-01-15  0:29                 ` brian m. carlson
2021-01-15  1:44                 ` Junio C Hamano
2021-01-16 16:23                 ` Ævar Arnfjörð Bjarmason
2021-01-17 17:15                   ` Jeff King
2021-01-17 20:22                     ` Ævar Arnfjörð Bjarmason
2021-01-10 19:00     ` Ævar Arnfjörð Bjarmason
2021-01-11  0:21       ` Junio C Hamano
2021-01-09 21:38 ` David Aguilar
2021-01-09 23:08   ` Junio C Hamano
2021-01-14 23:06 ` Emily Shaffer
2021-01-15  1:50   ` Junio C Hamano
2021-01-15  2:24     ` Taylor Blau
2021-01-15  2:44       ` Taylor Blau
2021-01-15  2:36   ` Derrick Stolee
2021-01-15  2:54     ` Derrick Stolee
2021-01-15  6:36     ` Junio C Hamano
2021-01-15  6:38       ` Junio C Hamano
2021-01-15 11:36         ` Derrick Stolee
2021-01-15 19:44           ` Junio C Hamano
2021-01-15 20:08             ` Emily Shaffer
2021-01-15 20:59               ` Junio C Hamano
2021-01-15 19:52 ` Jeff King
2021-01-15 21:40   ` Junio C Hamano

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=xmqqft32u0jp.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=emilyshaffer@google.com \
    --cc=git@vger.kernel.org \
    --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).