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

Re: [PATCH 1/3] docs: adjust for the recent rename of `pu` to `seen`

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 23, 2020, 19:31 UTC
Message-ID
<xmqq5zbhd1em.fsf@gitster.c.googlers.com>
In-Reply-To
<20200623153106.GB20455@danh.dev>
Đoàn Trần Công Danh  <congdanhqx@gmail.com> writes:
Show 17 quoted lines
> Hi Dscho,
>
> On 2020-06-23 15:04:13+0000, Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com> wrote:
>> diff --git a/Documentation/git-ls-remote.txt b/Documentation/git-ls-remote.txt
>> index 0a5c8b7d493..492e573856f 100644
>> --- a/Documentation/git-ls-remote.txt
>> +++ b/Documentation/git-ls-remote.txt
>> @@ -101,9 +101,9 @@ f25a265a342aed6041ab0cc484224d9ca54b6f41	refs/tags/v0.99.1
>>  7ceca275d047c90c0c7d5afb13ab97efdf51bd6e	refs/tags/v0.99.3
>>  c5db5456ae3b0873fc659c19fafdde22313cc441	refs/tags/v0.99.2
>>  0918385dbd9656cab0d1d81ba7453d49bbc16250	refs/tags/junio-gpg-pub
>> -$ git ls-remote http://www.kernel.org/pub/scm/git/git.git master pu rc
>> +$ git ls-remote http://www.kernel.org/pub/scm/git/git.git master seen rc
>
> rc is not with us anymore.
>
> Should we replace it with next, too?
I do not think so.  I think we never had 'rc'.
I think what the above example is demonstrating is this.
    SYNOPSIS calls the last command line arguments <refs>; they are
    actually mere patterns (which is how these command line
    arguments are described in the documentation).  It is *not* an
    error if no refs match a particular pattern.

And because we have no refs that match the pattern "rc", we only see "master" and "pu" (now "seen") from the command.

I see a couple of possible improvements here:
 - The "<refs>...::" documentation should explain what kind of
   pattern match is performed here.  I recall these originally were
   just tail matches, but the rule might have been made more
   flexible over time.
 - The example should first explain the setting.  The first sample
   depends on the current (./.) repository having these tags or it
   would not work (showing the sample upfront and explaining the
   outcome shown in the sample would work well in this case,
   e.g. "we can see that in the current repository, there are tags
   X, Y and Z").  The second one at least needs to say two things:
   the sample repository does not have a branch called 'rc' and that
   is why it is not shown, and it is not an error for patterns to
   produce no match.
Thanks.
Show 7 quoted lines
>
>>  5fe978a5381f1fbad26a80e682ddd2a401966740	refs/heads/master
>> -c781a84b5204fb294c9ccc79f8b3baceeb32c061	refs/heads/pu
>> +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
Previous: Đoàn Trần Công DanhNext: Johannes Schindelin
Message 4 of 30 in “Accommodate for pu having been renamed to seen”
  1. 0/3 Accommodate for pu having been renamed to seenJohannes Schindelin via GitGitGadget, Jun 23, 2020
  2. 1/3 docs: adjust for the recent rename of `pu` to `seen`Johannes Schindelin via GitGitGadget, Jun 23, 2020
  3. Đoàn Trần Công DanhJun 23, 2020
  4. Junio C HamanoJun 23, 2020
  5. Johannes SchindelinJun 23, 2020
  6. Đoàn Trần Công DanhJun 24, 2020
  7. 3/3 tests: reference `seen` wherever `pu` was referencedJohannes Schindelin via GitGitGadget, Jun 23, 2020
  8. 2/3 docs: adjust the technical overview for the rename `pu` -> `seen`Johannes Schindelin via GitGitGadget, Jun 23, 2020
  9. 0/3 Accommodate for pu having been renamed to seenJohannes Schindelin via GitGitGadget, Jun 24, 2020
  10. 1/3 docs: adjust for the recent rename of `pu` to `seen`Johannes Schindelin via GitGitGadget, Jun 24, 2020
  11. Denton LiuJun 24, 2020
  12. 2/3 docs: adjust the technical overview for the rename `pu` -> `seen`Johannes Schindelin via GitGitGadget, Jun 24, 2020
  13. 3/3 tests: reference `seen` wherever `pu` was referencedJohannes Schindelin via GitGitGadget, Jun 24, 2020
  14. Denton LiuJun 24, 2020
  15. Junio C HamanoJun 24, 2020
  16. Johannes SchindelinJun 29, 2020
  17. Junio C HamanoJun 24, 2020
  18. Junio C HamanoJun 24, 2020
  19. Denton LiuJun 24, 2020
  20. Junio C HamanoJun 24, 2020
  21. Johannes SchindelinJun 29, 2020
  22. 0/3 Accommodate for pu having been renamed to seenJohannes Schindelin via GitGitGadget, Jun 25, 2020
  23. 1/3 docs: adjust for the recent rename of `pu` to `seen`Johannes Schindelin via GitGitGadget, Jun 25, 2020
  24. 3/3 tests: reference `seen` wherever `pu` was referencedJohannes Schindelin via GitGitGadget, Jun 25, 2020
  25. 2/3 docs: adjust the technical overview for the rename `pu` -> `seen`Johannes Schindelin via GitGitGadget, Jun 25, 2020
  26. Junio C HamanoJun 25, 2020
  27. Johannes SchindelinJun 29, 2020
  28. Junio C HamanoJun 30, 2020
  29. Johannes SchindelinJul 1, 2020
  30. Update ProGit for pu -> seen change? (was Re: [PATCH v3 0/3] Accommodate for pu having been renamed to seen)Kaartic Sivaraam, Jun 26, 2020

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.