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

Re: [PATCH 2/2] add-patch: quit on EOF

From
René Scharfe <l.s.r@web.de>
Date
Oct 25, 2025, 17:23 UTC
Message-ID
<06b8485e-1e64-4c57-be3a-34b1f900c526@web.de>
In-Reply-To
<xmqqfrb7nebp.fsf@gitster.g>
On 10/25/25 6:20 PM, Junio C Hamano wrote:
Show 10 quoted lines
> 
> I wonder if we want to 'echo" something in this case, though.  If I
> say 'q', whether interactive.singlekey is active or not, I see
> 
>     (1/1) Stage this hunk [y,n,q,a,d,s,e,p,P,?]? q
> 
> on the last line before getting the shell prompt back.  With this
> change, I won't see anything after the prompt.  Perhaps it is OK?  I
> dunno.  Perhaps we want to pretend as if 'q' were given instead of
> EOF, like the following?  I dunno.

I'm used to no feedback when writing to a file using cat and finishing with ctrl-D to signal end-of-file. So I don't need a q "echoed", and would actually be slightly surprised. But that's just me.

René
Previous: Junio C HamanoNext: Junio C Hamano
Message 4 of 8 in “add-patch: quit without skipping undecided hunks”
  1. 1/2 add-patch: quit without skipping undecided hunksRené Scharfe, Oct 25, 2025
  2. 2/2 add-patch: quit on EOFRené Scharfe, Oct 25, 2025
  3. Junio C HamanoOct 25, 2025
  4. René ScharfeOct 25, 2025
  5. Junio C HamanoOct 26, 2025
  6. Junio C HamanoOct 26, 2025
  7. René ScharfeOct 26, 2025
  8. Junio C HamanoOct 25, 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.