Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 21 Apr 2002 00:38:14 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 21 Apr 2002 00:38:13 -0400 Received: from out020pub.verizon.net ([206.46.170.176]:50430 "EHLO out020.verizon.net") by vger.kernel.org with ESMTP id ; Sun, 21 Apr 2002 00:38:12 -0400 Date: Sun, 21 Apr 2002 00:40:11 -0400 From: Skip Ford To: linux-kernel@vger.kernel.org Cc: Linus Torvalds Subject: Re: BK, deltas, snapshots and fate of -pre... Mail-Followup-To: linux-kernel@vger.kernel.org, Linus Torvalds In-Reply-To: <20020421044616.5beae559.spyro@armlinux.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Message-Id: <20020421043811.BHIC5495.out020.verizon.net@pool-141-150-235-204.delv.east.verizon.net> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Alexander Viro wrote: > > As long as "I've got a bunch of patches affecting . Seeing that you've > merged stuff touching since the last -pre, resync point would be > a Good Thing(tm)" works I couldn't care less about BK vs. diff+mail. So > far it seems to be working fine. That's only 1 aspect. The frustrating part is bug reports mailed to the list getting a response of "oh, that's fixed in the latest bk tree." That's happened a dozen times in the last week...no wonder non-bk users feel out of the loop. I've been staring at the code for a lot of years and it's finally just starting to make sense to me, now by the time I see it the core hackers have moved on to something else. Daily snapshots would be great. -- Skip - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/