"J. Bruce Fields" <bfields@xxxxxxxxxxxx> writes:
> Clarify glossary definition of "reachable" (what chain?)
>
> Signed-off-by: "J. Bruce Fields" <bfields@xxxxxxxxxxxxxx>
> ---
> Documentation/glossary.txt | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/Documentation/glossary.txt b/Documentation/glossary.txt
> index 7c1a659..5886fa7 100644
> --- a/Documentation/glossary.txt
> +++ b/Documentation/glossary.txt
> @@ -236,7 +236,7 @@ push::
>
> reachable::
> An object is reachable from a ref/commit/tree/tag, if there is a
> - chain leading from the latter to the former.
> + chain of parent commits leading from the latter to the former.
That is better but the description is too commit centric.
The set of reachable objects from a tag is the tag
itself and the set of reachable objects from the object
it tags. The set of reachable objects from a commit is
the commit itself, and the set of reachable objects from
its parents and its tree. The set of reachable objects
from a tree is the tree itself, and the set of reachable
objects from the trees and blobs contained within it.
The set of reachable objects from a blob is the blob
itself.
And that description is too verbose and too technical
(definition being recursive). Better rewording?
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html