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

[GSoC PATCH v3 3/3] doc: gitprotocol-pack: normalize italic formatting

From
LorenzoPegorari <lorenzo.pegorari2002@gmail.com>
Date
Mar 3, 2026, 01:46 UTC
Message-ID
<2cf8a13eafd7d99d5633da95d62acd0c28af8c68.1772502209.git.lorenzo.pegorari2002@gmail.com>
In-Reply-To
<cover.1772502209.git.lorenzo.pegorari2002@gmail.com>
Uniform italic style usage for command and process names.
Signed-off-by: LorenzoPegorari <lorenzo.pegorari2002@gmail.com>
---
 Documentation/gitprotocol-pack.adoc | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/Documentation/gitprotocol-pack.adoc b/Documentation/gitprotocol-pack.adoc
index f4c9e024b0..633deecf2d 100644
--- a/Documentation/gitprotocol-pack.adoc
+++ b/Documentation/gitprotocol-pack.adoc
@@ -117,7 +117,7 @@ process on the server side over the Git protocol is this:
 SSH Transport
 -------------
 
-Initiating the upload-pack or receive-pack processes over SSH is
+Initiating the 'upload-pack' or 'receive-pack' processes over SSH is
 executing the binary on the server via SSH remote execution.
 It is basically equivalent to running this:
 
@@ -131,7 +131,7 @@ two commands, or even just one of them.
 
 In an ssh:// format URI, it's absolute in the URI, so the '/' after
 the host name (or port number) is sent as an argument, which is then
-read by the remote git-upload-pack exactly as is, so it's effectively
+read by the remote 'git-upload-pack' exactly as is, so it's effectively
 an absolute path in the remote filesystem.
 
        git clone ssh://user@example.com/project.git
@@ -163,7 +163,7 @@ supports passing environment variables as an argument.
 
 A few things to remember here:
 
-- The "command name" is spelled with dash (e.g. git-upload-pack), but
+- The "command name" is spelled with dash (e.g. 'git-upload-pack'), but
   this can be overridden by the client;
 
 - The repository path is always quoted with single quotes.
@@ -377,10 +377,10 @@ In multi_ack_detailed mode:
 
 Without either multi_ack or multi_ack_detailed:
 
- * upload-pack sends "ACK obj-id" on the first common object it finds.
+ * 'upload-pack' sends "ACK obj-id" on the first common object it finds.
    After that it says nothing until the client gives it a "done".
 
- * upload-pack sends "NAK" on a flush-pkt if no common object
+ * 'upload-pack' sends "NAK" on a flush-pkt if no common object
    has been found yet.  If one has been found, and thus an ACK
    was already sent, it's silent on the flush-pkt.
 
-- 
2.43.0
Previous: LorenzoPegorari
Message 15 of 15 in “doc: improve gitprotocol-pack”
  1. 0/3 doc: improve gitprotocol-packLorenzoPegorari, Mar 2, 2026
  2. 1/3 doc: gitprotocol-pack: fix pronoun-antecedent agreementLorenzoPegorari, Mar 2, 2026
  3. 2/3 doc: gitprotocol-pack: improve paragraphs structureLorenzoPegorari, Mar 2, 2026
  4. 3/3 doc: gitprotocol-pack: normalize inline code formattingLorenzoPegorari, Mar 2, 2026
  5. Junio C HamanoMar 2, 2026
  6. Lorenzo PegorariMar 3, 2026
  7. Junio C HamanoMar 3, 2026
  8. 0/3 doc: improve gitprotocol-packLorenzoPegorari, Mar 3, 2026
  9. 1/3 doc: gitprotocol-pack: fix pronoun-antecedent agreementLorenzoPegorari, Mar 3, 2026
  10. 2/3 doc: gitprotocol-pack: improve paragraphs structureLorenzoPegorari, Mar 3, 2026
  11. 3/3 doc: gitprotocol-pack: normalize italic formattingLorenzoPegorari, Mar 3, 2026
  12. 0/3 doc: improve gitprotocol-packLorenzoPegorari, Mar 3, 2026
  13. 1/3 doc: gitprotocol-pack: fix pronoun-antecedent agreementLorenzoPegorari, Mar 3, 2026
  14. 2/3 doc: gitprotocol-pack: improve paragraphs structureLorenzoPegorari, Mar 3, 2026
  15. 3/3 doc: gitprotocol-pack: normalize italic formattingLorenzoPegorari, Mar 3, 2026

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.