{"thread":{"id":"19955","subject":"git remote rm non-existant-remote","startedAt":"2009-06-28T14:47:23Z","lastAt":"2009-06-29T16:38:43Z","messageCount":4,"participants":["Brian Gernhardt","Jeff King"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"117129","messageId":"540FF00B-9DE7-4C89-9EC3-264B5BDD9CDE@silverinsanity.com","threadId":"19955","inReplyTo":null,"subject":"git remote rm non-existant-remote","fromName":"Brian Gernhardt","fromEmail":"benji@silverinsanity.com","sentAt":"2009-06-28T14:47:23Z","receivedAt":"2009-06-28T14:47:23Z","isPatch":false,"sender":{"key":"benji@silverinsanity.com","avatar":"https://gravatar.com/avatar/e06c101dbc25c68114d859b4a9ec7cf8a2c52fd2b0270ef0eac0e2e63ff22311?d=mp&s=160"},"body":"I was working on updating the remotes for one of my repositories  \n(adding a variety of forks) and renamed the origin branch.  When I was  \ndone, I tried to use \"git remote rm origin\" to remove the branches for  \nthe now dead origin.  What git-remote did was remove all of my remotes  \nand the merge information for my master branch (which was moved off  \nthe origin remote).\n\nThis is a data loss bug.  Very bad.  `git remote rm` should either  \nrefuse to remove a non-existent remote or (preferably) simply remove  \nany branches that exist for that remote.\n\nWhen time allows I'll look into fixing this, but I thought I'd post in  \ncase somebody had more tuits than me this week.\n\n~~ Brian Gernhardt\n"},{"id":"117133","messageId":"20090628161141.GA7796@sigio.peff.net","threadId":"19955","inReplyTo":"540FF00B-9DE7-4C89-9EC3-264B5BDD9CDE@silverinsanity.com","subject":"Re: git remote rm non-existant-remote","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2009-06-28T16:11:41Z","receivedAt":"2009-06-28T16:11:41Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Sun, Jun 28, 2009 at 10:47:23AM -0400, Brian Gernhardt wrote:\n\n> I was working on updating the remotes for one of my repositories\n> (adding a variety of forks) and renamed the origin branch.  When I\n> was done, I tried to use \"git remote rm origin\" to remove the\n> branches for the now dead origin.  What git-remote did was remove all\n> of my remotes and the merge information for my master branch (which\n> was moved off the origin remote).\n> \n> This is a data loss bug.  Very bad.  `git remote rm` should either\n> refuse to remove a non-existent remote or (preferably) simply remove\n> any branches that exist for that remote.\n\nOuch. That is indeed a serious bug. However, I can't reproduce with\ncurrent 'next'; which version of git are you using?\n\n> When time allows I'll look into fixing this, but I thought I'd post\n> in case somebody had more tuits than me this week.\n\nI think it would be nice to have it delete partial cruft left over, but\nI suspect just changing it to refuse the deletion will be a one-liner.\nIt would be nice to get at least that out to 'maint' branches as\nappropriate.\n\n-Peff\n"},{"id":"117147","messageId":"C1DD7597-AAFF-4F79-B11C-4D6BE9EB2601@silverinsanity.com","threadId":"19955","inReplyTo":"20090628161141.GA7796@sigio.peff.net","subject":"Re: git remote rm non-existant-remote","fromName":"Brian Gernhardt","fromEmail":"benji@silverinsanity.com","sentAt":"2009-06-28T23:04:17Z","receivedAt":"2009-06-28T23:04:17Z","isPatch":false,"sender":{"key":"benji@silverinsanity.com","avatar":"https://gravatar.com/avatar/e06c101dbc25c68114d859b4a9ec7cf8a2c52fd2b0270ef0eac0e2e63ff22311?d=mp&s=160"},"body":"\nOn Jun 28, 2009, at 12:11 PM, Jeff King wrote:\n\n> On Sun, Jun 28, 2009 at 10:47:23AM -0400, Brian Gernhardt wrote:\n>\n>> I was working on updating the remotes for one of my repositories\n>> (adding a variety of forks) and renamed the origin branch.  When I\n>> was done, I tried to use \"git remote rm origin\" to remove the\n>> branches for the now dead origin.  What git-remote did was remove all\n>> of my remotes and the merge information for my master branch (which\n>> was moved off the origin remote).\n>>\n>> This is a data loss bug.  Very bad.  `git remote rm` should either\n>> refuse to remove a non-existent remote or (preferably) simply remove\n>> any branches that exist for that remote.\n>\n> Ouch. That is indeed a serious bug. However, I can't reproduce with\n> current 'next'; which version of git are you using?\n\ngit version 1.6.3.3.467.g98a79\n\nI believe that's the latest \"next\".\n\n~~ Brian\n"},{"id":"117168","messageId":"20090629163842.GA12855@sigio.peff.net","threadId":"19955","inReplyTo":"C1DD7597-AAFF-4F79-B11C-4D6BE9EB2601@silverinsanity.com","subject":"Re: git remote rm non-existant-remote","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2009-06-29T16:38:43Z","receivedAt":"2009-06-29T16:38:43Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Sun, Jun 28, 2009 at 07:04:17PM -0400, Brian Gernhardt wrote:\n\n> >Ouch. That is indeed a serious bug. However, I can't reproduce with\n> >current 'next'; which version of git are you using?\n> \n> git version 1.6.3.3.467.g98a79\n> \n> I believe that's the latest \"next\".\n\nOK, then it is not a version problem, but rather I am doing something\ndifferent to try to reproduce it. Can you post a short set of commands\nto show the problem?\n\n-Peff\n"}]}