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

[RFC PATCH] user-manual: fix anchor name Finding-comments-With-given-Content

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Sep 28, 2010, 11:16 UTC
Message-ID
<f2cc250ea5816f351074bd0efb482398acb7428d.1285672508.git.git@drmicha.warpmail.net>
Change the anchor name to
Finding-commits-With-given-Content
so that it corresponds to the actual content there.
Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net>
---
The downside is that existing links go stale, of course.
Also, CapiTalisation is a bit weird but goes with prior art here.
 Documentation/user-manual.txt |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index fecc4eb..8d9a3c4 100644
--- a/Documentation/user-manual.txt
+++ b/Documentation/user-manual.txt
@@ -955,7 +955,7 @@ echo "git diff --stat --summary -M v$last v$new > ../diffstat-$new"
 and then he just cut-and-pastes the output commands after verifying that
 they look OK.
 
-[[Finding-comments-With-given-Content]]
+[[Finding-commits-With-given-Content]]
 Finding commits referencing a file with given content
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-- 
1.7.3.98.g5ad7d
Message 1 of 1 in “user-manual: fix anchor name Finding-comments-With-given-Content”
  1. user-manual: fix anchor name Finding-comments-With-given-ContentMichael J Gruber, Sep 28, 2010

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.