{"thread":{"id":"6272","subject":"[PATCH] Documentation: clarify glossary definition of \"reachable\"","startedAt":"2007-01-08T00:28:39Z","lastAt":"2007-01-08T03:28:45Z","messageCount":3,"participants":["J. Bruce Fields","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"31090","messageId":"20070108002839.GF18009@fieldses.org","threadId":"6272","inReplyTo":null,"subject":"[PATCH] Documentation: clarify glossary definition of \"reachable\"","fromName":"J. Bruce Fields","fromEmail":"bfields@fieldses.org","sentAt":"2007-01-08T00:28:39Z","receivedAt":"2007-01-08T00:28:39Z","isPatch":true,"sender":{"key":"bfields@citi.umich.edu","avatar":null},"body":"Clarify glossary definition of \"reachable\" (what chain?)\n\nSigned-off-by: \"J. Bruce Fields\" \n---\n Documentation/glossary.txt | 2 +-\n 1 files changed, 1 insertions(+), 1 deletions(-)\n\ndiff --git a/Documentation/glossary.txt b/Documentation/glossary.txt\nindex 7c1a659..5886fa7 100644\n--- a/Documentation/glossary.txt\n+++ b/Documentation/glossary.txt\n@@ -236,7 +236,7 @@ push::\n \n reachable::\n \tAn object is reachable from a ref/commit/tree/tag, if there is a\n-\tchain leading from the latter to the former.\n+\tchain of parent commits leading from the latter to the former.\n \n rebase::\n \tTo clean a branch by starting from the head of the main line of\n-- \n1.5.0.rc0.ge16c2\n"},{"id":"31098","messageId":"7vvejiz40u.fsf@assigned-by-dhcp.cox.net","threadId":"6272","inReplyTo":"20070108002839.GF18009@fieldses.org","subject":"Re: [PATCH] Documentation: clarify glossary definition of \"reachable\"","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2007-01-08T01:44:01Z","receivedAt":"2007-01-08T01:44:01Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"J. Bruce Fields\" writes:\n\n> Clarify glossary definition of \"reachable\" (what chain?)\n>\n> Signed-off-by: \"J. Bruce Fields\" \n> ---\n> Documentation/glossary.txt | 2 +-\n> 1 files changed, 1 insertions(+), 1 deletions(-)\n>\n> diff --git a/Documentation/glossary.txt b/Documentation/glossary.txt\n> index 7c1a659..5886fa7 100644\n> --- a/Documentation/glossary.txt\n> +++ b/Documentation/glossary.txt\n> @@ -236,7 +236,7 @@ push::\n> \n> reachable::\n> \tAn object is reachable from a ref/commit/tree/tag, if there is a\n> -\tchain leading from the latter to the former.\n> +\tchain of parent commits leading from the latter to the former.\n\nThat is better but the description is too commit centric.\n\n The set of reachable objects from a tag is the tag\n itself and the set of reachable objects from the object\n it tags. The set of reachable objects from a commit is\n the commit itself, and the set of reachable objects from\n its parents and its tree. The set of reachable objects\n from a tree is the tree itself, and the set of reachable\n objects from the trees and blobs contained within it.\n The set of reachable objects from a blob is the blob\n itself.\n\nAnd that description is too verbose and too technical\n(definition being recursive). Better rewording?\n"},{"id":"31113","messageId":"20070108032845.GJ18009@fieldses.org","threadId":"6272","inReplyTo":"7vvejiz40u.fsf@assigned-by-dhcp.cox.net","subject":"Re: [PATCH] Documentation: clarify glossary definition of \"reachable\"","fromName":"J. Bruce Fields","fromEmail":"bfields@fieldses.org","sentAt":"2007-01-08T03:28:45Z","receivedAt":"2007-01-08T03:28:45Z","isPatch":true,"sender":{"key":"bfields@citi.umich.edu","avatar":null},"body":"On Sun, Jan 07, 2007 at 05:44:01PM -0800, Junio C Hamano wrote:\n> That is better but the description is too commit centric.\n> \n> The set of reachable objects from a tag is the tag\n> itself and the set of reachable objects from the object\n> it tags. The set of reachable objects from a commit is\n> the commit itself, and the set of reachable objects from\n> its parents and its tree. The set of reachable objects\n> from a tree is the tree itself, and the set of reachable\n> objects from the trees and blobs contained within it.\n> The set of reachable objects from a blob is the blob\n> itself.\n> \n> And that description is too verbose and too technical\n> (definition being recursive). Better rewording?\n\nOops, you're right! Take two: (I'm still giving the commit case first\nas a special example, because I think it's the most important case, and\nbecause it requires less knowledge to understand.)\n\n--b.\n\n>From 1b1885dc3cf597452c597f34e6f52856c9524239 Mon Sep 17 00:00:00 2001\nFrom: J. Bruce Fields \nDate: Sun, 7 Jan 2007 19:25:35 -0500\nSubject: [PATCH] [PATCH] Documentation: clarify definition of \"reachable\"\n\nClarify definition of \"reachable\" (what chain?)\n\nSigned-off-by: \"J. Bruce Fields\" \n---\n Documentation/glossary.txt | 7 +++++--\n 1 files changed, 5 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/glossary.txt b/Documentation/glossary.txt\nindex 7c1a659..cd61aa2 100644\n--- a/Documentation/glossary.txt\n+++ b/Documentation/glossary.txt\n@@ -235,8 +235,11 @@ push::\n \tlocal head, the push fails.\n \n reachable::\n-\tAn object is reachable from a ref/commit/tree/tag, if there is a\n-\tchain leading from the latter to the former.\n+\tAll of the ancestors of a given commit are said to be reachable from\n+\tthat commit. More generally, one object is reachable from another if\n+\twe can reach the one from the other by a chain that follows tags to\n+\twhatever they tag, commits to their parents or trees, and trees to the\n+\ttrees or blobs that they contain.\n \n rebase::\n \tTo clean a branch by starting from the head of the main line of\n-- \n1.5.0.rc0.ge16c2\n"}]}