threads / discuss / 19955

git remote rm non-existant-remote

Subject: git remote rm non-existant-remote

## tl;dr

4 messages between Jun 28, 2009 and Jun 29, 2009.

replies: 3people: 2as markdown or json

Brian Gernhardt· Jun 28, 2009, 14:47 UTC · lore

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

Jeff King· Jun 28, 2009, 16:11 UTC · re: Brian Gernhardt · lore

Re: git remote rm non-existant-remote

On Sun, Jun 28, 2009 at 10:47:23AM -0400, Brian Gernhardt wrote:

Show 10 quoted lines

> 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.

Ouch. That is indeed a serious bug. However, I can't reproduce with current 'next'; which version of git are you using?

> 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.

I think it would be nice to have it delete partial cruft left over, but I suspect just changing it to refuse the deletion will be a one-liner. It would be nice to get at least that out to 'maint' branches as appropriate.

-Peff

Brian Gernhardt· Jun 28, 2009, 23:04 UTC · re: Jeff King · lore

Re: git remote rm non-existant-remote

On Jun 28, 2009, at 12:11 PM, Jeff King wrote:

Show 15 quoted lines

> On Sun, Jun 28, 2009 at 10:47:23AM -0400, Brian Gernhardt wrote:
>
>> 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.
>
> Ouch. That is indeed a serious bug. However, I can't reproduce with
> current 'next'; which version of git are you using?

git version 1.6.3.3.467.g98a79

I believe that's the latest "next".

~~ Brian

Jeff King· Jun 29, 2009, 16:38 UTC · re: Brian Gernhardt · lore

Re: git remote rm non-existant-remote

On Sun, Jun 28, 2009 at 07:04:17PM -0400, Brian Gernhardt wrote:

Show 6 quoted lines

> >Ouch. That is indeed a serious bug. However, I can't reproduce with
> >current 'next'; which version of git are you using?
> 
> git version 1.6.3.3.467.g98a79
> 
> I believe that's the latest "next".

OK, then it is not a version problem, but rather I am doing something different to try to reproduce it. Can you post a short set of commands to show the problem?

-Peff