git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v3 0/7] documentation cleanups for <rev>^{<type>}

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 4, 2013, 22:27 UTC
Message-ID
<xmqq8uzckysx.fsf@gitster.dls.corp.google.com>
In-Reply-To
<1378321474-7125-1-git-send-email-rhansen@bbn.com>
Richard Hansen <rhansen@bbn.com> writes:
Show 16 quoted lines
> On 2013-09-03 18:46, Junio C Hamano wrote:
>> I hate to say this after seeing you doing a thorough job in this
>> series, but because "tree-ish" and "commit-ish" are both made-up
>> words, I have a feeling that we are better off unifying to the
>> dashed form, which unfortunately is the other way around from what
>> your series does.
>
> I thought you might say that so I held on to the commits that
> standardize on tree-ish and commit-ish in my local repo.  :)
>
> This series still says "tree-ish (also treeish)" and "commit-ish (also
> committish)" in gitglossary(7).  Would you like me to eliminate the
> "(also ...)"  part?
>
> I'm not 100% confident that these don't break translations, although
> it still builds and "make test" passes.
We will find out ;-)
Show 15 quoted lines
> Changes since v2:
>   * standardize on 'tree-ish' instead of 'treeish'
>   * standardize on 'commit-ish' instead of 'committish'
>
> Richard Hansen (7):
>   glossary: mention 'treeish' as an alternative to 'tree-ish'
>   glossary: define commit-ish (a.k.a. committish)
>   use 'tree-ish' instead of 'treeish'
>   use 'commit-ish' instead of 'committish'
>   glossary: more precise definition of tree-ish (a.k.a. treeish)
>   revisions.txt: fix and clarify <rev>^{<type>}
>   glossary: fix and clarify the definition of 'ref'
>
>  Documentation/RelNotes/1.7.11.2.txt          |  2 +-
>  Documentation/howto/revert-branch-rebase.txt |  2 +-

I generally prefer not to touch historical documents but the change in this series is small enough that I think it is OK.

Thanks, will queue.
Previous: Richard HansenNext: Richard Hansen
Message 12 of 18 in “documentation cleanups for <rev>^{<type>}”
  1. 0/7 documentation cleanups for <rev>^{<type>}Richard Hansen, Sep 2, 2013
  2. 1/7 glossary: mention 'treeish' as an alternative to 'tree-ish'Richard Hansen, Sep 2, 2013
  3. Junio C HamanoSep 3, 2013
  4. 0/7 documentation cleanups for <rev>^{<type>}Richard Hansen, Sep 4, 2013
  5. 1/7 glossary: mention 'treeish' as an alternative to 'tree-ish'Richard Hansen, Sep 4, 2013
  6. 2/7 glossary: define commit-ish (a.k.a. committish)Richard Hansen, Sep 4, 2013
  7. 3/7 use 'tree-ish' instead of 'treeish'Richard Hansen, Sep 4, 2013
  8. 4/7 use 'commit-ish' instead of 'committish'Richard Hansen, Sep 4, 2013
  9. 5/7 glossary: more precise definition of tree-ish (a.k.a. treeish)Richard Hansen, Sep 4, 2013
  10. 6/7 revisions.txt: fix and clarify <rev>^{<type>}Richard Hansen, Sep 4, 2013
  11. 7/7 glossary: fix and clarify the definition of 'ref'Richard Hansen, Sep 4, 2013
  12. Junio C HamanoSep 4, 2013
  13. 2/7 glossary: define committish (a.k.a. commit-ish)Richard Hansen, Sep 2, 2013
  14. 3/7 use 'treeish' instead of 'tree-ish'Richard Hansen, Sep 2, 2013
  15. 4/7 use 'committish' instead of 'commit-ish'Richard Hansen, Sep 2, 2013
  16. 5/7 glossary: more precise definition of treeish (a.k.a. tree-ish)Richard Hansen, Sep 2, 2013
  17. 6/7 revisions.txt: fix and clarify <rev>^{<type>}Richard Hansen, Sep 2, 2013
  18. 7/7 glossary: fix and clarify the definition of 'ref'Richard Hansen, Sep 2, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.