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

[PATCH v3 1/4] glossary: remove outdated/misleading/irrelevant entries

From
Thomas Ackermann <th.acker@arcor.de>
Date
Apr 15, 2013, 17:46 UTC
Message-ID
<1456791522.996464.1366048016249.JavaMail.ngmail@webmail19.arcor-online.net>
In-Reply-To
<46832203.996447.1366047902197.JavaMail.ngmail@webmail19.arcor-online.net>
Signed-off-by: Thomas Ackermann <th.acker@arcor.de>
---
 Documentation/glossary-content.txt | 11 +----------
 1 file changed, 1 insertion(+), 10 deletions(-)
diff --git a/Documentation/glossary-content.txt b/Documentation/glossary-content.txt
index eb7ba84..5a7a486 100644
--- a/Documentation/glossary-content.txt
+++ b/Documentation/glossary-content.txt
@@ -104,9 +104,6 @@ to point at the new commit.
 	an arbitrary <<def_commit,commit>> that isn't necessarily the tip of any
 	particular branch.  In this case HEAD is said to be "detached".
 
-[[def_dircache]]dircache::
-	You are *waaaaay* behind. See <<def_index,index>>.
-
 [[def_directory]]directory::
 	The list you get with "ls" :-)
 
@@ -115,11 +112,6 @@ to point at the new commit.
 	it contains modifications which have not been <<def_commit,committed>> to the current
 	<<def_branch,branch>>.
 
-[[def_ent]]ent::
-	Favorite synonym to "<<def_tree-ish,tree-ish>>" by some total geeks. See
-	http://en.wikipedia.org/wiki/Ent_(Middle-earth) for an in-depth
-	explanation. Avoid this term, not to confuse people.
-
 [[def_evil_merge]]evil merge::
 	An evil merge is a <<def_merge,merge>> that introduces changes that
 	do not appear in any <<def_parent,parent>>.
@@ -257,8 +249,7 @@ This commit is referred to as a "merge commit", or sometimes just a
 	<<def_object,object>>.
 
 [[def_octopus]]octopus::
-	To <<def_merge,merge>> more than two <<def_branch,branches>>. Also denotes an
-	intelligent predator.
+	To <<def_merge,merge>> more than two <<def_branch,branches>>.
 
 [[def_origin]]origin::
 	The default upstream <<def_repository,repository>>. Most projects have
-- 
1.8.1.msysgit.1


---
Thomas
Previous: Thomas AckermannNext: Junio C Hamano
Message 2 of 10 in “Some small fixes to glossary-content.txt”
  1. 0/4 Some small fixes to glossary-content.txtThomas Ackermann, Apr 15, 2013
  2. 1/4 glossary: remove outdated/misleading/irrelevant entriesThomas Ackermann, Apr 15, 2013
  3. Junio C HamanoApr 15, 2013
  4. 2/4 glossary: improve description of SHA-1 related topicsThomas Ackermann, Apr 15, 2013
  5. 3/4 The name of the hash function is "SHA-1", not "SHA1"Thomas Ackermann, Apr 15, 2013
  6. Junio C HamanoApr 15, 2013
  7. Michael HaggertyApr 16, 2013
  8. 4/4 glossary: improve definitions of refspec and pathspecThomas Ackermann, Apr 15, 2013
  9. Junio C HamanoApr 15, 2013
  10. Aw: Re: [PATCH v3 4/4] glossary: improve definitions of refspec and pathspecThomas Ackermann, Apr 15, 2013

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.