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

git remote rm non-existant-remote

From
Brian Gernhardt <benji@silverinsanity.com>
Date
Jun 28, 2009, 14:47 UTC
Message-ID
<540FF00B-9DE7-4C89-9EC3-264B5BDD9CDE@silverinsanity.com>

I was working on updating the remotes for one of my repositories (adding a variety of forks) and renamed the origin branch. When I was done, I tried to use "git remote rm origin" to remove the branches for the now dead origin. What git-remote did was remove all of my remotes and the merge information for my master branch (which was moved off the origin remote).

This is a data loss bug. Very bad. `git remote rm` should either refuse to remove a non-existent remote or (preferably) simply remove any branches that exist for that remote.

When time allows I'll look into fixing this, but I thought I'd post in case somebody had more tuits than me this week.

~~ Brian Gernhardt
Next: Jeff King
Message 1 of 4 in “git remote rm non-existant-remote”
  1. Brian GernhardtJun 28, 2009
  2. Jeff KingJun 28, 2009
  3. Brian GernhardtJun 28, 2009
  4. Jeff KingJun 29, 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.