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

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

From
Uusharerose <ushareroses@gmail.com>
Date
Sep 15, 2025, 13:40 UTC
Message-ID
<CAJKmQvcUQnsgcWW5EgUEaDwZKdtWXnJ1aoVQTAdvG3+te5p1ug@mail.gmail.com>
In-Reply-To
<62774477-81d2-4959-aa5f-fe0dca023a2a@app.fastmail.com>

On Sun, Sep 14, 2025 at 7:58 PM Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com> wrote:

> What’s the positive case for email validation?

Thanks for your reply, Kris. My intention behind the original question was not to suggest adding 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.

I've come across many explanations, but they mostly list the various application scenarios for `user.email` value. I haven't found an officially recognized answer regarding whether the above applications were explicitly considered during the initial design phase. Therefore, I would like to consult the official community here.

Thank you again for your help.
Previous: Kristoffer Haugsbakk
Message 14 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.