Skip to content

Commit 69fb960

Browse files
peffgitster
authored andcommitted
document 'quiet' receive-pack capability
This was added in c207e34 (fix push --quiet: add 'quiet' capability to receive-pack, 2012-01-08) but never documented. Signed-off-by: Jeff King <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent af60826 commit 69fb960

File tree

1 file changed

+11
-1
lines changed

1 file changed

+11
-1
lines changed

Documentation/technical/protocol-capabilities.txt

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ was sent. Server MUST NOT ignore capabilities that client requested
1818
and server advertised. As a consequence of these rules, server MUST
1919
NOT advertise capabilities it does not understand.
2020

21-
The 'report-status' and 'delete-refs' capabilities are sent and
21+
The 'report-status', 'delete-refs', and 'quiet' capabilities are sent and
2222
recognized by the receive-pack (push to server) process.
2323

2424
The 'ofs-delta' and 'side-band-64k' capabilities are sent and recognized
@@ -200,3 +200,13 @@ it is capable of accepting a zero-id value as the target
200200
value of a reference update. It is not sent back by the client, it
201201
simply informs the client that it can be sent zero-id values
202202
to delete references.
203+
204+
quiet
205+
-----
206+
207+
If the receive-pack server advertises the 'quiet' capability, it is
208+
capable of silencing human-readable progress output which otherwise may
209+
be shown when processing the received pack. A send-pack client should
210+
respond with the 'quiet' capability to suppress server-side progress
211+
reporting if the local progress reporting is also being suppressed
212+
(e.g., via `push -q`, or if stderr does not go to a tty).

0 commit comments

Comments
 (0)