Re: [DISCUSS] validation on git config user.email

From: usharerose <ushareroses@gmail.com>
Date: Sep 12, 2025, 18:06 UTC
Message-ID: <CAJKmQvd1r3NvWKnswHFBf-HJ+H63wBhKF-Q2VABZAbvUXacUQw@mail.gmail.com>
In-Reply-To: <xmqqtt17my71.fsf@gitster.g>

On Sat, Sep 13, 2025 at 12:29 AM Junio C Hamano <gitster@pobox.com> wrote:

> That is a very good point.  We need to remember that not all users
> use the value of the field we define to be "email" to send emails
> to, just like some people use "name" field to store something that
> is not their name.

Thanks for your reply, Junio.

My intention behind the original question was not to suggest adding the feature of validation for email legitimacy, but rather to inquire about and understand the rationale behind the initial design decision to forgo strict validation when the user identity feature (user.email) was implemented.

So, is the case ("not all users use the value of the field we define to be 'email' to send emails to") more of a case of "exploiting a perceived backdoor that later became justified" or "a thoughtfully made design decision from the beginning"?