From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 10 May 2002 13:58:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 10 May 2002 13:58:19 -0400 Received: from zeke.inet.com ([199.171.211.198]:10211 "EHLO zeke.inet.com") by vger.kernel.org with ESMTP id ; Fri, 10 May 2002 13:58:15 -0400 Message-ID: <3CDC0A34.2000006@inet.com> Date: Fri, 10 May 2002 12:58:12 -0500 From: Eli Carter User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020311 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Larry McVoy CC: linux-kernel@vger.kernel.org Subject: Re: BK problem In-Reply-To: <200205101725.g4AHPOH05574@work.bitmover.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Larry McVoy wrote: > Hi, we've got a problem in one of Linus' trees and it has started to > propagate around. I need your help to track it down and fix it. > Please run the following script on your Linux BK trees and contact > me if it tells you to do so. You can fix up the tree by doing the > following (warning: takes lots and lots of CPU time so if you don't > need the tree it may well be faster to reclone tomorrow after I finish > fixing the trees on bkbits). Would you mind giving something of a lay-man's explanation of what went wrong and what that means? In particular, I'm curious about the propagating part... Eli --------------------. "If it ain't broke now, Eli Carter \ it will be soon." -- crypto-gram eli.carter(a)inet.com `-------------------------------------------------