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

Update ProGit for pu -> seen change? (was Re: [PATCH v3 0/3] Accommodate for pu having been renamed to seen)

From
Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Date
Jun 26, 2020, 09:06 UTC
Message-ID
<c08504e9-5067-221b-819c-adce262c7394@gmail.com>
In-Reply-To
<pull.668.v3.git.1593087539.gitgitgadget@gmail.com>
On 25-06-2020 17:48, Johannes Schindelin via GitGitGadget wrote:
Show 5 quoted lines
> This patch series adjusts Git's own source code to reflect that change.
> 
> Please note that even with these patches, there are still a couple places
> where pu is used:
>

This reminds me. The ProGit book references the `pu` branch in several places in the text and images IIRC. Is it fine to change them now? Would it be premature?

Show 5 quoted lines
>  * In the translations. These are legitimate words in languages that are not
>    English (as in "gpg n'a pas pu signer les données" where "pu" is French
>    for the English "could").
>  * In upload-pack.c, where a variable named pu is short form for
>    "pack-objects updates".
-- 
Sivaraam
Previous: Johannes Schindelin
Message 30 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.