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

[PATCH 2/2] unpack-trees.c: align submodule error message to the other error messages

From
Stefan Beller <sbeller@google.com>
Date
Mar 29, 2017, 18:37 UTC
Message-ID
<20170329183743.27506-2-sbeller@google.com>
In-Reply-To
<20170329183743.27506-1-sbeller@google.com>

As the place holder in the error message is for multiple submodules, we don't want to encapsulate the string place holder in single quotes.

Signed-off-by: Stefan Beller <sbeller@google.com>
---
 unpack-trees.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/unpack-trees.c b/unpack-trees.c
index 8333da2cc9..9f386cc174 100644
--- a/unpack-trees.c
+++ b/unpack-trees.c
@@ -167,7 +167,7 @@ void setup_unpack_trees_porcelain(struct unpack_trees_options *opts,
 	msgs[ERROR_WOULD_LOSE_ORPHANED_REMOVED] =
 		_("The following working tree files would be removed by sparse checkout update:\n%s");
 	msgs[ERROR_WOULD_LOSE_SUBMODULE] =
-		_("Submodule '%s' cannot checkout new HEAD");
+		_("The following submodules cannot checkout a new HEAD:\n%s");
 
 	opts->show_all_errors = 1;
 	/* rejected paths may not have a static buffer */
-- 
2.12.0.rc1.52.g2de7d24de9.dirty
Previous: Stefan BellerNext: Jonathan Nieder
Message 2 of 8 in “entry.c: submodule recursing: respect force flag correctly”
  1. 1/2 entry.c: submodule recursing: respect force flag correctlyStefan Beller, Mar 29, 2017
  2. 2/2 unpack-trees.c: align submodule error message to the other error messagesStefan Beller, Mar 29, 2017
  3. Jonathan NiederMar 29, 2017
  4. Junio C HamanoMar 29, 2017
  5. unpack-trees.c: align submodule error message to the other error messagesStefan Beller, Mar 29, 2017
  6. Junio C HamanoMar 29, 2017
  7. Jonathan NiederMar 29, 2017
  8. Junio C HamanoMar 29, 2017

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.