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

Re: [PATCH v3 4/6] ls-remote doc: show peeled tags in examples

From
Junio C Hamano <gitster@pobox.com>
Date
May 15, 2023, 19:53 UTC
Message-ID
<xmqqlehp8j7r.fsf@gitster.g>
In-Reply-To
<dc0c5ba17511628b384d7c2d6d5eb43342017b5d.1684152793.git.gitgitgadget@gmail.com>
"Sean Allred via GitGitGadget" <gitgitgadget@gmail.com> writes:
Show 10 quoted lines
> From: Sean Allred <allred.sean@gmail.com>
>
> Without `--refs`, this command will show peeled tags. Make this clearer
> in the examples to further mitigate the possibility of surprises in
> consuming scripts.
>
> Signed-off-by: Sean Allred <allred.sean@gmail.com>
> ---
>  Documentation/git-ls-remote.txt | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
Nice attention to the detail.  Thanks.
Show 19 quoted lines
> diff --git a/Documentation/git-ls-remote.txt b/Documentation/git-ls-remote.txt
> index af71cf4a92d..aabc1a7b90b 100644
> --- a/Documentation/git-ls-remote.txt
> +++ b/Documentation/git-ls-remote.txt
> @@ -106,10 +106,10 @@ c781a84b5204fb294c9ccc79f8b3baceeb32c061	refs/heads/seen
>  
>  $ git remote add korg http://www.kernel.org/pub/scm/git/git.git
>  $ git ls-remote --tags korg v\*
> -d6602ec5194c87b0fc87103ca4d67251c76f233a	refs/tags/v0.99
> -f25a265a342aed6041ab0cc484224d9ca54b6f41	refs/tags/v0.99.1
> -c5db5456ae3b0873fc659c19fafdde22313cc441	refs/tags/v0.99.2
> -7ceca275d047c90c0c7d5afb13ab97efdf51bd6e	refs/tags/v0.99.3
> +485a869c64a68cc5795dd99689797c5900f4716d	refs/tags/v2.39.2
> +cbf04937d5b9fcf0a76c28f69e6294e9e3ecd7e6	refs/tags/v2.39.2^{}
> +d4ca2e3147b409459955613c152220f4db848ee1	refs/tags/v2.40.0
> +73876f4861cd3d187a4682290ab75c9dccadbc56	refs/tags/v2.40.0^{}
>  ----
>  
>  SEE ALSO
Previous: Sean Allred via GitGitGadgetNext: Sean Allred via GitGitGadget
Message 23 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.