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

[PATCH 3/4] document 'agent' protocol capability

From
Jeff King <peff@peff.net>
Date
Jul 24, 2013, 08:03 UTC
Message-ID
<20130724080313.GC4425@sigill.intra.peff.net>
In-Reply-To
<20130724080051.GA3890@sigill.intra.peff.net>

This was added in ff5effd (include agent identifier in capability string, 2012-08-03), but neither the syntax nor the semantics were ever documented outside of the commit message.

Signed-off-by: Jeff King <peff@peff.net>
---
 Documentation/technical/protocol-capabilities.txt | 17 ++++++++++++++++-
 1 file changed, 16 insertions(+), 1 deletion(-)
diff --git a/Documentation/technical/protocol-capabilities.txt b/Documentation/technical/protocol-capabilities.txt
index 9bc2a10..d35159e 100644
--- a/Documentation/technical/protocol-capabilities.txt
+++ b/Documentation/technical/protocol-capabilities.txt
@@ -22,7 +22,8 @@ The 'ofs-delta' and 'side-band-64k' capabilities are sent and recognized
 recognized by the receive-pack (push to server) process.
 
 The 'ofs-delta' and 'side-band-64k' capabilities are sent and recognized
-by both upload-pack and receive-pack protocols.
+by both upload-pack and receive-pack protocols.  The 'agent' capability
+may optionally be sent in both protocols.
 
 All other capabilities are only recognized by the upload-pack (fetch
 from server) process.
@@ -123,6 +124,20 @@ send/read OBJ_OFS_DELTA (aka type 6) in a packfile.
 its base by position in pack rather than by an obj-id.  That is, they can
 send/read OBJ_OFS_DELTA (aka type 6) in a packfile.
 
+agent
+-----
+
+The server may optionally send a capability of the form `agent=X` to
+notify the client that the server is running version `X`. The client may
+optionally return its own agent string by responding with an `agent=Y`
+capability (but it MUST NOT do so if the server did not mention the
+agent capability). The `X` and `Y` strings may contain any printable
+ASCII characters except space (i.e., the byte range 32 < x < 127), and
+are typically of the form "package/version" (e.g., "git/1.8.3.1"). The
+agent strings are purely informative for statistics and debugging
+purposes, and MUST NOT be used to programatically assume the presence
+or absence of particular features.
+
 shallow
 -------
 
-- 
1.8.3.rc1.30.gff0fb75
Previous: Jeff KingNext: Jeff King
Message 6 of 9 in “Missing capabilities in Documentation/technical/protocol-capbilities.txt”
  1. Duy NguyenJul 15, 2013
  2. Clemens BuchacherJul 17, 2013
  3. 0/4 protocol-capabilities documentation updatesJeff King, Jul 24, 2013
  4. 1/4 docs: fix 'report-status' protocol capability thinkoJeff King, Jul 24, 2013
  5. 2/4 docs: note that receive-pack knows side-band-64k capabilityJeff King, Jul 24, 2013
  6. 3/4 document 'agent' protocol capabilityJeff King, Jul 24, 2013
  7. 4/4 document 'quiet' receive-pack capabilityJeff King, Jul 24, 2013
  8. 5/4 document 'allow-tip-sha1-in-want' capabilityNguyễn Thái Ngọc Duy, Jul 26, 2013
  9. Junio C HamanoJul 26, 2013

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.