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

[PATCHv2 3/8] Doc: Improve shallow depth wording

From
Philip Oakley <philipoakley@iee.org>
Date
Sep 18, 2012, 23:25 UTC
Message-ID
<1348010734-664-4-git-send-email-philipoakley@iee.org>

Avoid confusion in compound sentence about the start of the commit set and the depth measure. Use two sentences.

Signed-off-by: Philip Oakley <philipoakley@iee.org>
diff --git a/Documentation/technical/pack-protocol.txt b/Documentation/technical/pack-protocol.txt
index 49cdc57..d51e20f 100644
--- a/Documentation/technical/pack-protocol.txt
+++ b/Documentation/technical/pack-protocol.txt
@@ -259,8 +259,10 @@ a positive depth, this step is skipped.
 ----
 
 If the client has requested a positive depth, the server will compute
-the set of commits which are no deeper than the desired depth, starting
-at the client's wants. The server writes 'shallow' lines for each
+the set of commits which are no deeper than the desired depth. The set
+of commits start at the client's wants.
+
+The server writes 'shallow' lines for each
 commit whose parents will not be sent as a result. The server writes
 an 'unshallow' line for each commit which the client has indicated is
 shallow, but is no longer shallow at the currently requested depth

-- 
1.7.8.msysgit.0
Message 1 of 1 in “[PATCHv2 3/8] Doc: Improve shallow depth wording”
  1. Philip OakleySep 18, 2012

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.