From: Brian Gernhardt <benji@silverinsanity.com>
Date: Sun, 28 Jun 2009 23:04:17 GMT
Subject: Re: git remote rm non-existant-remote
Message-ID: <C1DD7597-AAFF-4F79-B11C-4D6BE9EB2601@silverinsanity.com>
In-Reply-To: <20090628161141.GA7796@sigio.peff.net>


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

> 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