On 2013-06-19 13:09, Junio C Hamano wrote: > Richard Hansen <rhansen@xxxxxxx> 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. I can s/treeish/tree-ish/g, although I'd still like to keep 'treeish' in the glossary so that people can find it when they search for the misspelled version. Perhaps something like: -[[def_tree-ish]]tree-ish:: +[[def_tree-ish]]tree-ish (sometimes misspelled treeish):: would be satisfactory? While we're on the topic, do you have a preference for commit-ish vs. committish? Grepping the code shows comittish to be the overwhelming favorite, but it's inconsistent with tree-ish. -Richard > >> >> Signed-off-by: Richard Hansen <rhansen@xxxxxxx> >> --- >> 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 majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- 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