All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yasushi SHOJI <yashi@atmark-techno.com>
To: git@vger.kernel.org
Subject: Add dangling object and unreachable object in glossary.txt
Date: Mon, 05 Mar 2007 03:07:43 +0900	[thread overview]
Message-ID: <87649g991s.wl@mail2.atmark-techno.com> (raw)
In-Reply-To: Pine.LNX.4.64.0702261216380.12485@woody.linux-foundation.org

---
Would it be worth to add these two entery in
Documentation/glossary.txt?

English isn't my mother tang, so please check it.
-- 
         yashi



diff --git a/Documentation/glossary.txt b/Documentation/glossary.txt
index d20eb62..ee48009 100644
--- a/Documentation/glossary.txt
+++ b/Documentation/glossary.txt
@@ -73,6 +73,11 @@ DAG::
 	objects is acyclic (there is no chain which begins and ends with the
 	same object).
 
+dangling object::
+	An object which is a very special case of unreachable object;
+	it is not reachable from anything, including unreachable
+	objects.
+
 dircache::
 	You are *waaaaay* behind.
 
@@ -350,6 +355,9 @@ tag::
 unmerged index::
 	An index which contains unmerged index entries.
 
+unreachable object::
+	An object which is not reachable.
+
 working tree::
 	The set of files and directories currently being worked on,
 	i.e. you can work in your working tree without using git at all.

  reply	other threads:[~2007-03-04 18:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-26 16:35 Isn't "dangling" a misnomer? Mike Coleman
2007-02-26 17:02 ` Johannes Schindelin
2007-02-26 20:03 ` Junio C Hamano
2007-02-26 20:19   ` Linus Torvalds
2007-03-04 18:07     ` Yasushi SHOJI [this message]
2007-03-04 19:03       ` Add dangling object and unreachable object in glossary.txt Josef Sipek
2007-03-04 21:27       ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87649g991s.wl@mail2.atmark-techno.com \
    --to=yashi@atmark-techno.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.