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

[PATCH] Documentation/git-fsck.txt: fix typo: unreadable -> unreachable

From
Jim Meyering <jim@meyering.net>
Date
May 16, 2011, 18:23 UTC
Message-ID
<874o4uwllk.fsf@rho.meyering.net>
Signed-off-by: Jim Meyering <meyering@redhat.com>
---
 Documentation/git-fsck.txt |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-fsck.txt b/Documentation/git-fsck.txt
index c9ede79..a2a508d 100644
--- a/Documentation/git-fsck.txt
+++ b/Documentation/git-fsck.txt
@@ -26,7 +26,7 @@ index file, all SHA1 references in .git/refs/*, and all reflogs (unless
 --no-reflogs is given) as heads.

 --unreachable::
-	Print out objects that exist but that aren't readable from any
+	Print out objects that exist but that aren't reachable from any
 	of the reference nodes.

 --root::
@@ -76,7 +76,7 @@ It tests SHA1 and general object sanity, and it does full tracking of
 the resulting reachability and everything else. It prints out any
 corruption it finds (missing or bad objects), and if you use the
 '--unreachable' flag it will also print out objects that exist but
-that aren't readable from any of the specified head nodes.
+that aren't reachable from any of the specified head nodes.

 So for example

--
1.7.5.1.467.g1a85
Message 1 of 1 in “Documentation/git-fsck.txt: fix typo: unreadable -> unreachable”
  1. Documentation/git-fsck.txt: fix typo: unreadable -> unreachableJim Meyering, May 16, 2011

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.