Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 21 Apr 2002 12:35:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 21 Apr 2002 12:35:34 -0400 Received: from twinlark.arctic.org ([208.44.199.239]:36063 "EHLO twinlark.arctic.org") by vger.kernel.org with ESMTP id ; Sun, 21 Apr 2002 12:35:32 -0400 Date: Sun, 21 Apr 2002 09:35:31 -0700 (PDT) From: dean gaudet To: Skip Ford cc: linux-kernel@vger.kernel.org Subject: Re: BK, deltas, snapshots and fate of -pre... In-Reply-To: <20020421043811.BHIC5495.out020.verizon.net@pool-141-150-235-204.delv.east.verizon.net> Message-ID: X-comment: visit http://arctic.org/~dean/legal for information regarding copyright and disclaimer. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 21 Apr 2002, Skip Ford wrote: > 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." in the pre-bk past i've seen "that's fixed in my tree" with no reference to how to get "my tree" -- this repeated by many folks, including linus. for those of you with issues against using bk, you should just pretend that's what you're reading. you can even respond with "could you make a snapshot available?" like folks used to. you can even go pick up the new daily snapshots. so your frustration is either not a new thing, or has been solved. -dean - 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/