{"thread":{"id":"3277","subject":"RE: Fatal error from git bisect","startedAt":"2006-02-09T21:21:27Z","lastAt":"2006-02-09T21:32:40Z","messageCount":2,"participants":["Mark E Mason","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"15807","messageId":"7E000E7F06B05C49BDBB769ADAF44D0773A4BC@NT-SJCA-0750.brcm.ad.broadcom.com","threadId":"3277","inReplyTo":null,"subject":"RE: Fatal error from git bisect","fromName":"Mark E Mason","fromEmail":"mark.e.mason@broadcom.com","sentAt":"2006-02-09T21:21:27Z","receivedAt":"2006-02-09T21:21:27Z","isPatch":false,"sender":{"key":"mark.e.mason@broadcom.com","avatar":null},"body":"Hello, \n\n> From: Linus Torvalds [mailto:torvalds@osdl.org] \n[snip]\n> Now, it could be a git bug, but before you go there, try to \n> make sure tat your tree is really clean. Do a\n> \n> \tgit checkout -f master\n> \n> followed by \"git status\" to make sure that the workspace is \n> clean (no unexpected untracked files, no diffs against HEAD, \n> no nothing). The \"git checkout -f master\" should have cleaned \n> everything up, but it won't actually touch extra files that \n> it doesn't know about, so..\n\nThat did the trick.  Thanks very much for the pointer, it's much\nappreciated.\n\nThanks,\nMark\n"},{"id":"15808","messageId":"7vvevo8bgn.fsf@assigned-by-dhcp.cox.net","threadId":"3277","inReplyTo":"7E000E7F06B05C49BDBB769ADAF44D0773A4BC@NT-SJCA-0750.brcm.ad.broadcom.com","subject":"Re: Fatal error from git bisect","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-02-09T21:32:40Z","receivedAt":"2006-02-09T21:32:40Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"Mark E Mason\" <mark.e.mason@broadcom.com> writes:\n\n> That did the trick.  Thanks very much for the pointer, it's much\n> appreciated.\n\nThanks, both of you.  This got me worried, especially when I am\nat work and cannot pull the whole mips tree to take a look at it\nmyself.\n"}]}