{"thread":{"id":"4045","subject":"[WARNING] please stop using git.git \"next\" for now","startedAt":"2006-05-03T21:53:31Z","lastAt":"2006-05-04T00:46:42Z","messageCount":3,"participants":["Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"19471","messageId":"7virombwro.fsf@assigned-by-dhcp.cox.net","threadId":"4045","inReplyTo":null,"subject":"[WARNING] please stop using git.git \"next\" for now","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-05-03T21:53:31Z","receivedAt":"2006-05-03T21:53:31Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"I just noticed there is a breakage in write-tree optimization\nthat uses the new cache-tree data structure in the \"next\"\nbranch.  Switching branches with \"git checkout anotherbranch\"\nwhen your index exactly matches the current HEAD commit and then\nimmediately doing write-tree produces a nonsense tree, and\ncommits on top of that results in tree objects that have\nduplicated entries.\n\nI will be working on a fix now, but in the meantime please do\nnot use the \"next\" branch for real work.  Sorry for the\nbreakage.\n"},{"id":"19480","messageId":"7vejzabt2b.fsf@assigned-by-dhcp.cox.net","threadId":"4045","inReplyTo":"7virombwro.fsf@assigned-by-dhcp.cox.net","subject":"Re: [WARNING] please stop using git.git \"next\" for now","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-05-03T23:13:32Z","receivedAt":"2006-05-03T23:13:32Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Junio C Hamano <junkio@cox.net> writes:\n\n> I just noticed there is a breakage in write-tree optimization\n> that uses the new cache-tree data structure in the \"next\"\n> branch.  Switching branches with \"git checkout anotherbranch\"\n> when your index exactly matches the current HEAD commit and then\n> immediately doing write-tree produces a nonsense tree, and\n> commits on top of that results in tree objects that have\n> duplicated entries.\n>\n> I will be working on a fix now, but in the meantime please do\n> not use the \"next\" branch for real work.  Sorry for the\n> breakage.\n\nTwo-way merge by read-tree forgot to invalidate the directories\na new element was added underneath.  The fix is simple and will\nbe in the \"next\" I'll push out tonight.\n\nSorry for the noise.\n"},{"id":"19487","messageId":"7vwtd2aa6l.fsf@assigned-by-dhcp.cox.net","threadId":"4045","inReplyTo":"7vejzabt2b.fsf@assigned-by-dhcp.cox.net","subject":"Re: [WARNING] please stop using git.git \"next\" for now","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-05-04T00:46:42Z","receivedAt":"2006-05-04T00:46:42Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Junio C Hamano <junkio@cox.net> writes:\n\n>> I will be working on a fix now, but in the meantime please do\n>> not use the \"next\" branch for real work.  Sorry for the\n>> breakage.\n>\n> Two-way merge by read-tree forgot to invalidate the directories\n> a new element was added underneath.  The fix is simple and will\n> be in the \"next\" I'll push out tonight.\n\nOK, done.  Will be looking into \"binary grep segfault\" problem\nnext.\n"}]}