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

Re: renaming remote branches

From
Miles Bader <miles@gnu.org>
Date
Apr 17, 2009, 00:51 UTC
Message-ID
<buomyagf6g7.fsf@dhlpc061.dev.necel.com>
In-Reply-To
<20090416135037.GA7770@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
> All of that is assuming that remote renames are common enough to really
> care about. Personally, I've never actually done one.

The use-case which prompted my question was "retiring" obsolete branches that exist on a public server (which is usually only interactived with remotely using git).

E.g., a project has a long-term public branch "oink" which is finally merged to master, and thereafter ceases to be kept up-to-date. Sometimes the developers are reluctant to delete it becaue they want to keep the history around. However simply leaving it in place can be pretty confusing, as people tend to keep downloading it, not realizing how out-of-date it is. A nice compromise is to rename "oink" to "obsolete/oink", which keeps around the history for easy perusal, but makes the status of the branch pretty clear at a glance.

-Miles
-- 
Yo mama's so fat when she gets on an elevator it HAS to go down.
Previous: Jeff KingNext: Jeff King
Message 7 of 9 in “renaming remote branches”
  1. Miles BaderApr 16, 2009
  2. Jeff KingApr 16, 2009
  3. Miles BaderApr 16, 2009
  4. Jeff KingApr 16, 2009
  5. Jay SoffianApr 16, 2009
  6. Jeff KingApr 16, 2009
  7. Miles BaderApr 17, 2009
  8. Jeff KingApr 17, 2009
  9. Dmitry PotapovApr 17, 2009

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.