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

Re: [PATCH v3 6/6] ls-remote doc: document the output format

From
Junio C Hamano <gitster@pobox.com>
Date
May 15, 2023, 20:01 UTC
Message-ID
<xmqqfs7x8iu4.fsf@gitster.g>
In-Reply-To
<de57b8aa563f20b45e18dbe45abaa14a2971da13.1684152793.git.gitgitgadget@gmail.com>
"Sean Allred via GitGitGadget" <gitgitgadget@gmail.com> writes:
Show 33 quoted lines
> From: Sean Allred <allred.sean@gmail.com>
>
> While well-established, the output format of ls-remote was not actually
> documented. This patch adds an OUTPUT section to the documentation
> following the format of git-show-ref.txt (which has similar semantics).
>
> Add a basic example immediately after this to solidify the 'normal'
> output format.
>
> Signed-off-by: Sean Allred <allred.sean@gmail.com>
> ---
>  Documentation/git-ls-remote.txt | 24 ++++++++++++++++++++++++
>  1 file changed, 24 insertions(+)
>
> diff --git a/Documentation/git-ls-remote.txt b/Documentation/git-ls-remote.txt
> index c0b2facef48..15313f2b10d 100644
> --- a/Documentation/git-ls-remote.txt
> +++ b/Documentation/git-ls-remote.txt
> @@ -96,9 +96,33 @@ OPTIONS
>  	separator (so `bar` matches `refs/heads/bar` but not
>  	`refs/heads/foobar`).
>  
> +OUTPUT
> +------
> +
> +The output is in the format:
> +
> +------------
> +<oid> TAB <ref> LF
> +------------
> +
> +When `<ref>` is a tag, it may be followed by `^{}` to show its peeled
> +representation.

While I can guess what the above wants to say, the above does not quite "click" for me for some reason. Here is my attempt.

    When showing an annotated tag, unless `--refs` is given, two
    such lines are shown, one with the refname for the tag itself as
    <ref>, and another with <ref> followed by `^{}`.  The `<oid>` on
    the latter line shows the name of the object the tag points at.

The verb `peel` is used in the explanation for the `--refs` option, but there is no formal definition of what it means in the glossary.

We may want to do something about it, but we probably would want to leave it outside the scope of this series.

Other than that, looking great.
Thanks.
Previous: Sean Allred via GitGitGadgetNext: Sean Allred
Message 25 of 33 in “Document the output format of ls-remote”
  1. Document the output format of ls-remoteSean Allred via GitGitGadget, Mar 18, 2023
  2. Eric SunshineMar 19, 2023
  3. Felipe ContrerasMar 19, 2023
  4. Sean AllredMar 19, 2023
  5. 0/2 Document the output format of ls-remoteSean Allred via GitGitGadget, Mar 22, 2023
  6. 2/2 Document the output format of ls-remoteSean Allred via GitGitGadget, Mar 22, 2023
  7. Junio C HamanoMar 22, 2023
  8. Re* [PATCH v2 2/2] Document the output format of ls-remoteJunio C Hamano, Mar 22, 2023
  9. 1/2 Update show-ref documentation for internal consistencySean Allred via GitGitGadget, Mar 22, 2023
  10. Junio C HamanoMar 22, 2023
  11. 0/6 Document the output format of ls-remoteSean Allred via GitGitGadget, May 15, 2023
  12. 2/6 show-branch doc: say <ref>, not <reference>Junio C Hamano via GitGitGadget, May 15, 2023
  13. 1/6 show-ref doc: update for internal consistencySean Allred via GitGitGadget, May 15, 2023
  14. Eric SunshineMay 15, 2023
  15. Junio C HamanoMay 15, 2023
  16. Sean AllredMay 19, 2023
  17. Junio C HamanoMay 15, 2023
  18. Sean AllredMay 19, 2023
  19. 3/6 ls-remote doc: remove redundant --tags exampleSean Allred via GitGitGadget, May 15, 2023
  20. Junio C HamanoMay 15, 2023
  21. 5/6 ls-remote doc: explain what each example doesSean Allred via GitGitGadget, May 15, 2023
  22. 4/6 ls-remote doc: show peeled tags in examplesSean Allred via GitGitGadget, May 15, 2023
  23. Junio C HamanoMay 15, 2023
  24. 6/6 ls-remote doc: document the output formatSean Allred via GitGitGadget, May 15, 2023
  25. Junio C HamanoMay 15, 2023
  26. Sean AllredMay 19, 2023
  27. 0/6 Document the output format of ls-remoteSean Allred via GitGitGadget, May 19, 2023
  28. 1/6 show-ref doc: update for internal consistencySean Allred via GitGitGadget, May 19, 2023
  29. 2/6 show-branch doc: say <ref>, not <reference>Junio C Hamano via GitGitGadget, May 19, 2023
  30. 3/6 ls-remote doc: remove redundant --tags exampleSean Allred via GitGitGadget, May 19, 2023
  31. 4/6 ls-remote doc: show peeled tags in examplesSean Allred via GitGitGadget, May 19, 2023
  32. 5/6 ls-remote doc: explain what each example doesSean Allred via GitGitGadget, May 19, 2023
  33. 6/6 ls-remote doc: document the output formatSean Allred via GitGitGadget, May 19, 2023

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.