Re: renaming remote branches

[Miles Bader <miles@gnu.org>]

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.