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

Re: [PATCH] send-email: do not prompt for In-Reply-To

From
Drew DeVault <sir@cmpwn.com>
Date
Aug 27, 2020, 19:34 UTC
Message-ID
<C5814BWVXMP3.1GJ83FMKYSFTY@homura>
In-Reply-To
<xmqqtuwnq3x1.fsf@gitster.c.googlers.com>

Do you think this whole workstream could be averted by dropping the $prompting check in the in-reply-to branch?

Or would that still constitute a breaking change to user workflows?
Previous: Junio C HamanoNext: Carlo Arenas
Message 11 of 29 in “send-email: do not prompt for In-Reply-To”
  1. send-email: do not prompt for In-Reply-ToDrew DeVault, Aug 27, 2020
  2. Junio C HamanoAug 27, 2020
  3. Junio C HamanoAug 27, 2020
  4. Drew DeVaultAug 27, 2020
  5. Junio C HamanoAug 27, 2020
  6. Drew DeVaultAug 27, 2020
  7. Carlo Marcelo Arenas BelónAug 27, 2020
  8. Drew DeVaultAug 27, 2020
  9. Carlo Marcelo Arenas BelónAug 27, 2020
  10. Junio C HamanoAug 27, 2020
  11. Drew DeVaultAug 27, 2020
  12. Carlo ArenasAug 27, 2020
  13. Carlo Marcelo Arenas BelónAug 27, 2020
  14. Junio C HamanoAug 27, 2020
  15. Drew DeVaultAug 27, 2020
  16. Drew DeVaultAug 27, 2020
  17. Junio C HamanoAug 28, 2020
  18. Drew DeVaultAug 28, 2020
  19. Raymond E. PascoAug 28, 2020
  20. Drew DeVaultAug 28, 2020
  21. Junio C HamanoAug 27, 2020
  22. Drew DeVaultAug 27, 2020
  23. Drew DeVaultAug 28, 2020
  24. Junio C HamanoAug 28, 2020
  25. Drew DeVaultAug 28, 2020
  26. Junio C HamanoAug 28, 2020
  27. Drew DeVaultAug 28, 2020
  28. Raymond E. PascoAug 28, 2020
  29. Drew DeVaultAug 27, 2020

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.