git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 12, 2025, 16:29 UTC
Message-ID
<xmqqtt17my71.fsf@gitster.g>
In-Reply-To
<071101dc23f5$fbf06e30$f3d14a90$@nexbridge.com>
<rsbecker@nexbridge.com> writes:
> Some customers integrate single sign-on (SSO) via the user.email value. In the case
> of one customer I helped, the value is an SSO token used by GitHub for their
> integration. The token value does not conform to any valid email address format.
> Adding an email validation will lock them out of using git.

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.

Previous: rsbecker@nexbridge.comNext: usharerose
Message 3 of 14 in “[DISCUSS] validation on git config user.email”
  1. ushareroseSep 12, 2025
  2. rsbecker@nexbridge.comSep 12, 2025
  3. Junio C HamanoSep 12, 2025
  4. ushareroseSep 12, 2025
  5. ushareroseSep 12, 2025
  6. rsbecker@nexbridge.comSep 12, 2025
  7. ushareroseSep 12, 2025
  8. Kristoffer HaugsbakkSep 14, 2025
  9. rsbecker@nexbridge.comSep 14, 2025
  10. Konstantin RyabitsevSep 12, 2025
  11. Thomas GuyotSep 12, 2025
  12. ushareroseSep 12, 2025
  13. Kristoffer HaugsbakkSep 14, 2025
  14. ushareroseSep 15, 2025

Read the whole thread, see it on lore, or plain text.

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