Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 4 Oct 2002 20:07:23 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 4 Oct 2002 20:07:23 -0400 Received: from pizda.ninka.net ([216.101.162.242]:39394 "EHLO pizda.ninka.net") by vger.kernel.org with ESMTP id ; Fri, 4 Oct 2002 20:07:22 -0400 Date: Fri, 04 Oct 2002 17:04:51 -0700 (PDT) Message-Id: <20021004.170451.27090459.davem@redhat.com> To: zippel@linux-m68k.org Cc: gilbertd@treblig.org, lm@work.bitmover.com, tom_gall@mac.com, linux-kernel@vger.kernel.org Subject: Re: New BK License Problem? From: "David S. Miller" In-Reply-To: References: <20021004221639.GM710@gallifrey> X-FalunGong: Information control. X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 972 Lines: 29 From: Roman Zippel Date: Sat, 5 Oct 2002 00:36:16 +0200 (CEST) On Fri, 4 Oct 2002, Dr. David Alan Gilbert wrote: > Just to be clear; ... this is completely offtopic, can this _please_ be moved to a bk list? Thanks. It is very ontopic because it affects a number of kernel developers. Whether you like BK or not, it is the primary source management tool used by Linus and others, it is even documented in the source tree as such. Therefore, such a license change could change that, so it's a relavant topic. And finally, as the person who has to maintain this list and deal with the daily bounce pool this list generates every day, I declare it as ontopic so :-P~~~~~~ - 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/