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

[PATCH 1/3] Print newline for git-send-email --git-completion-helper.

From
Thiago Perrotta <tbperrotta@gmail.com>
Date
Aug 2, 2021, 20:49 UTC
Message-ID
<20210802204953.229867-2-tbperrotta@gmail.com>
In-Reply-To
<20210802204953.229867-1-tbperrotta@gmail.com>
Rationale: All git built-in commands print a newline upon upon git <cmd>
--git-completion-helper. Therefore git-send-email should follow suit for
consistency.
Signed-off-by: Thiago Perrotta <tbperrotta@gmail.com>
---
 git-send-email.perl | 1 +
 1 file changed, 1 insertion(+)
diff --git a/git-send-email.perl b/git-send-email.perl
index e65d969..e991bf3 100755
--- a/git-send-email.perl
+++ b/git-send-email.perl
@@ -115,6 +115,7 @@ sub usage {
 
 sub completion_helper {
     print Git::command('format-patch', '--git-completion-helper');
+    print "\n";
     exit(0);
 }
 
-- 
2.32.0
Previous: Thiago PerrottaNext: Thiago Perrotta
Message 2 of 4 in “git-send-email options and completion improvements”
  1. 0/3 git-send-email options and completion improvementsThiago Perrotta, Aug 2, 2021
  2. 1/3 Print newline for git-send-email --git-completion-helper.Thiago Perrotta, Aug 2, 2021
  3. 2/3 Move bash git-send-email completions to original script.Thiago Perrotta, Aug 2, 2021
  4. 3/3 Expand git-send-email docs to mention format-patch options.Thiago Perrotta, Aug 2, 2021

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.