Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 6 Oct 2002 17:25:59 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 6 Oct 2002 17:25:56 -0400 Received: from news.cistron.nl ([62.216.30.38]:40203 "EHLO ncc1701.cistron.net") by vger.kernel.org with ESMTP id ; Sun, 6 Oct 2002 17:25:55 -0400 From: "Miquel van Smoorenburg" Subject: Re: New BK License Problem? Date: Sun, 6 Oct 2002 21:31:02 +0000 (UTC) Organization: Cistron Message-ID: References: <20021006075627.I9032@work.bitmover.com> Content-Type: text/plain; charset=iso-8859-15 X-Trace: ncc1701.cistron.net 1033939862 13156 62.216.29.67 (6 Oct 2002 21:31:02 GMT) X-Complaints-To: abuse@cistron.nl X-Newsreader: trn 4.0-test76 (Apr 2, 2001) Originator: miquels@cistron-office.nl (Miquel van Smoorenburg) To: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 859 Lines: 14 In article , Ingo Molnar wrote: >so BK cannot be used to access the kernel tree in that case, correct? I'm >just wondering where the boundary line is. Eg. if i started working on a >versioned filesystem today, i'd not be allowed to use BK. I just have to >keep stuff like that in mind when using BK. And what if that versioning filesystem got accepted into mainline? Every kernel developer would have to buy a BK license. Either that or a versioning filesystem cannot get into mainline. Sorry Hans, no reiser4 in the kernel. Mike. - 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/