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 28, 2020, 21:01 UTC
Message-ID
<C58XLLAE3SMA.3T1C6DXZ4VSWA@homura>
In-Reply-To
<xmqqk0xio59r.fsf@gitster.c.googlers.com>
On Fri Aug 28, 2020 at 5:00 PM EDT, Junio C Hamano wrote:
Show 12 quoted lines
> "Drew DeVault" <sir@cmpwn.com> writes:
>
> > "You can give an empty answer if you are not responding to any message"
> > could confuse users, because they might think -v2 is a "response", or
> > maybe they've written the patch in response to a discussion on the
> > -users mailing list, or any other number of reasons.
>
> "Type the value you would have given to --in-reply-to command line
> option (if you forgot to use it), or leave this field empty"
> perhaps? Those who do not know should be able to learn what
> "--in-reply-to" is. A prompt help is not the place to do a
> documentation.

This would be better, yeah, but at that point it's pretty weird, like why are we prompting for this CLI flag and not any others? The answer is just for legacy reasons. There's no inherent justification for it.

Show 7 quoted lines
> > I hate to be a nuisance over such a seemingly simple problem, but there
> > are a lot of new users who are struggling here and I care about their
> > struggle. What path should we take to fixing this issue for them?
>
> The ideal way would be to craft step (0) well enough so that new
> users trigger the To: prompt in the first place, which would
> automatically make the problem disappear ;-)

Do you mean teaching users how to use --to upfront? Honestly the prompt seems totally fine to me, there's nothing wrong with a use-case which calls for typing your To address into the prompt. Hell, often I'll use it, or I'll use --annotate and write my To addresses in vim.

Previous: Junio C HamanoNext: Junio C Hamano
Message 25 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.