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

[PATCH] status merge: guarentee space between msg and path

From
Sandy Carter <sandy.carter@savoirfairelinux.com>
Date
Mar 11, 2014, 16:30 UTC
Message-ID
<1394555447-1805-1-git-send-email-sandy.carter@savoirfairelinux.com>

Add space between how and one when printing status of unmerged data. This fixes an appending of the how message when it is longer than 20. This is the case in some translations such as the french one where the colon gets appended to the file:

    supprimé par nous :wt-status.c
    modifié des deux côtés :wt-status.h

Additionally, having a space makes the file in question easier to select in console to quickly address the problem. Without the space, the colon (and, sometimes the last word) of the message is selected along with the file.

The previous french example should now print as the following, which is more proper:

    supprimé par nous : wt-status.c
    modifié des deux côtés : wt-status.h
Signed-off-by: Sandy Carter <sandy.carter@savoirfairelinux.com>
---
 wt-status.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/wt-status.c b/wt-status.c
index a452407..69e0dfc 100644
--- a/wt-status.c
+++ b/wt-status.c
@@ -264,7 +264,7 @@ static void wt_status_print_unmerged_data(struct wt_status *s,
 	case 6: how = _("both added:"); break;
 	case 7: how = _("both modified:"); break;
 	}
-	status_printf_more(s, c, "%-20s%s\n", how, one);
+	status_printf_more(s, c, "%-19s %s\n", how, one);
 	strbuf_release(&onebuf);
 }
 
-- 
1.9.0
Next: Junio C Hamano
Message 1 of 10 in “status merge: guarentee space between msg and path”
  1. status merge: guarentee space between msg and pathSandy Carter, Mar 11, 2014
  2. Junio C HamanoMar 11, 2014
  3. Sandy CarterMar 11, 2014
  4. Junio C HamanoMar 11, 2014
  5. Duy NguyenMar 11, 2014
  6. Junio C HamanoMar 12, 2014
  7. status merge: guarentee space between msg and pathSandy Carter, Mar 11, 2014
  8. Junio C HamanoMar 12, 2014
  9. Sandy CarterMar 12, 2014
  10. Junio C HamanoMar 12, 2014

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.