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

[PATCH] send-pack: unify error messages for unsupported capabilities

From
Ralf Thielow <ralf.thielow@gmail.com>
Date
Apr 2, 2015, 17:28 UTC
Message-ID
<1427995728-8162-1-git-send-email-ralf.thielow@gmail.com>

If --signed is not supported, the error message names the remote "receiving end". If --atomic is not supported, the error message names the remote "server". Unify the naming to "receiving end" as we're in the context of "push".

Signed-off-by: Ralf Thielow <ralf.thielow@gmail.com>
---
 send-pack.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/send-pack.c b/send-pack.c
index 9d2b0c5..189bdde 100644
--- a/send-pack.c
+++ b/send-pack.c
@@ -356,21 +356,21 @@ int send_pack(struct send_pack_args *args,
 			die(_("the receiving end does not support --signed push"));
 		push_cert_nonce = xmemdupz(push_cert_nonce, len);
 	}
 
 	if (!remote_refs) {
 		fprintf(stderr, "No refs in common and none specified; doing nothing.\n"
 			"Perhaps you should specify a branch such as 'master'.\n");
 		return 0;
 	}
 	if (args->atomic && !atomic_supported)
-		die(_("server does not support --atomic push"));
+		die(_("the receiving end does not support --atomic push"));
 
 	use_atomic = atomic_supported && args->atomic;
 
 	if (status_report)
 		strbuf_addstr(&cap_buf, " report-status");
 	if (use_sideband)
 		strbuf_addstr(&cap_buf, " side-band-64k");
 	if (quiet_supported && (args->quiet || !args->progress))
 		strbuf_addstr(&cap_buf, " quiet");
 	if (use_atomic)
-- 
2.4.0.rc0.243.g0be2dd7
Next: Junio C Hamano
Message 1 of 2 in “send-pack: unify error messages for unsupported capabilities”
  1. send-pack: unify error messages for unsupported capabilitiesRalf Thielow, Apr 2, 2015
  2. Junio C HamanoApr 2, 2015

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.