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

Re: Plumbing to rename a ref?

From
Junio C Hamano <gitster@pobox.com>
Date
May 23, 2014, 17:11 UTC
Message-ID
<xmqqr43kju8o.fsf@gitster.dls.corp.google.com>
In-Reply-To
<20140523123503.GB726@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 8 quoted lines
> One thing that this misses (as does your original script) is the
> reflogs. Doing "branch -m" to rename a branch will actually move the
> reflogs, too, but there is otherwise no way to access that
> functionality.
>
> It does not seem unreasonable to teach "git update-ref" to do renames to
> take advantage of this (it would be fairly simple; the logic is already
> encapsulated internally in a rename_ref function).
Sounds sensible.
Previous: Jeff KingNext: Jeff King
Message 5 of 8 in “Plumbing to rename a ref?”
  1. Sergei OrganovMay 23, 2014
  2. John KeepingMay 23, 2014
  3. Sergei OrganovMay 23, 2014
  4. Jeff KingMay 23, 2014
  5. Junio C HamanoMay 23, 2014
  6. Jeff KingMay 23, 2014
  7. Junio C HamanoMay 23, 2014
  8. John KeepingMay 23, 2014

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.