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

Re: [PATCH v2 0/3] Accommodate for pu having been renamed to seen

From
Denton Liu <liu.denton@gmail.com>
Date
Jun 24, 2020, 17:24 UTC
Message-ID
<20200624172425.GA152115@generichostname>
In-Reply-To
<xmqqd05o75so.fsf@gitster.c.googlers.com>
On Wed, Jun 24, 2020 at 10:05:43AM -0700, Junio C Hamano wrote:
> I do not know how many of you regularly have interacted with 'pu'
> and now need to go through the same adjustment as I do.  Sorry for
> using you as a guinea pig for an experiment for you know what to
> gauge the cost.
Heh, I was wondering if you had any ulterior motives ;)

Since we're on the topic of the cost of renaming branches, I was reading a reply from you back in 2011 about how HEAD symrefs are the only valid ones[0]. I'm not sure if the situation has changed since then but perhaps we could officially expand the scope of symrefs to allow users to essentially alias branches? It might reduce the cost of performing branch renames by having a backwards compatible option.

[0]: https://lore.kernel.org/git/7vsjvpq0jk.fsf@alter.siamese.dyndns.org/
Previous: Junio C HamanoNext: Junio C Hamano
Message 19 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.