Richard Hansen <rhan...@bbn.com> writes: > The documentation contains a mix of the two spellings, and including > both makes it possible for users to search the glossary with their > spelling of choice.
Is it an option to instead find dashless form in our documentation and turn all of them into tree-ish form with a dash? I personally find it cleaner that way. > > Signed-off-by: Richard Hansen <rhan...@bbn.com> > --- > Documentation/glossary-content.txt | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Documentation/glossary-content.txt > b/Documentation/glossary-content.txt > index db2a74d..01365d9 100644 > --- a/Documentation/glossary-content.txt > +++ b/Documentation/glossary-content.txt > @@ -486,7 +486,7 @@ should not be combined with other pathspec. > with refs to the associated blob and/or tree objects. A > <<def_tree,tree>> is equivalent to a <<def_directory,directory>>. > > -[[def_tree-ish]]tree-ish:: > +[[def_tree-ish]]tree-ish (also treeish):: > A <<def_ref,ref>> pointing to either a <<def_commit_object,commit > object>>, a <<def_tree_object,tree object>>, or a <<def_tag_object,tag > object>> pointing to a tag or commit or tree object. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
