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

[PATCH] user-manual: Use def_ instead of ref_ for glossary references.

From
JFJ. Bruce Fields <bfields@citi.umich.edu>
Date
Mar 19, 2007, 03:17 UTC
Message-ID
<39327.3101807155$1174274338@news.gmane.org>
In-Reply-To
<11742742813855-git-send-email->
From: J. Bruce Fields <bfields@citi.umich.edu>

I'd like to start using references to the glossary in the user manual. The "ref_" prefix for these references seems a little generic; so replace with "def_".

Signed-off-by: "J. Bruce Fields" <bfields@citi.umich.edu>
---
 Documentation/sort_glossary.pl |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/sort_glossary.pl b/Documentation/sort_glossary.pl
index 05dc7b2..4ae6290 100644
--- a/Documentation/sort_glossary.pl
+++ b/Documentation/sort_glossary.pl
@@ -50,8 +50,8 @@ This list is sorted alphabetically:
 @keys=sort {uc($a) cmp uc($b)} keys %terms;
 $pattern='(\b(?<!link:git-)'.join('\b|\b(?<!-)',reverse @keys).'\b)';
 foreach $key (@keys) {
-	$terms{$key}=~s/$pattern/sprintf "<<ref_".no_spaces($1).",$1>>";/eg;
-	print '[[ref_'.no_spaces($key).']]'.$key."::\n"
+	$terms{$key}=~s/$pattern/sprintf "<<def_".no_spaces($1).",$1>>";/eg;
+	print '[[def_'.no_spaces($key).']]'.$key."::\n"
 		.format_tab_80($terms{$key})."\n";
 }
 
-- 
1.5.0.3.31.ge47c
Previous: J. Bruce FieldsNext: J. Bruce Fields
Message 3 of 9 in “user-manual: run xsltproc without --nonet option”
  1. user-manual: run xsltproc without --nonet optionJ. Bruce Fields, Mar 19, 2007
  2. user-manual.txt: fix a tiny typo.J. Bruce Fields, Mar 19, 2007
  3. user-manual: Use def_ instead of ref_ for glossary references.J. Bruce Fields, Mar 19, 2007
  4. glossary: stop generating automaticallyJ. Bruce Fields, Mar 19, 2007
  5. glossary: clean up cross-referencesJ. Bruce Fields, Mar 19, 2007
  6. user-manual: introduce "branch" and "branch head" differentlyJ. Bruce Fields, Mar 19, 2007
  7. Junio C HamanoMar 19, 2007
  8. Johannes SchindelinMar 19, 2007
  9. Johannes SchindelinMar 19, 2007

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.