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

[DISCUSS] validation on git config user.email

From
Uusharerose <ushareroses@gmail.com>
Date
Sep 12, 2025, 04:13 UTC
Message-ID
<CAJKmQvf-sLxowLJLitvqDmyL1BXXDK+anDE2jaBSEabApMNVoQ@mail.gmail.com>
Hi, Git Community,

I'm a Git user and curious about a specific aspect of Git's design regarding the 'user.email' configuration.

Git allows any kind of values without restriction when setting 'user.email' via 'git config' (e.g., `git config user.email "not-a-valid-email-address"`).

I'm interested in understanding the design philosophy or historical reasons behind this 'lack' of validation.

I've glanced through the documentations, archived emails, or forum topics, but couldn't find a definitive or official statement.

Thanks for your time and insights.
Next: rsbecker@nexbridge.com
Message 1 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.