Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 16 Feb 2003 05:59:27 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 16 Feb 2003 05:59:27 -0500 Received: from [81.2.122.30] ([81.2.122.30]:11524 "EHLO darkstar.example.net") by vger.kernel.org with ESMTP id ; Sun, 16 Feb 2003 05:59:26 -0500 From: John Bradford Message-Id: <200302161108.h1GB8t8m000317@darkstar.example.net> Subject: Re: openbkweb-0.0 To: alan@lxorguk.ukuu.org.uk (Alan Cox) Date: Sun, 16 Feb 2003 11:08:55 +0000 (GMT) Cc: lm@bitmover.com, arashi@yomerashi.yi.org, linux-kernel@vger.kernel.org In-Reply-To: <1045372937.6051.1.camel@irongate.swansea.linux.org.uk> from "Alan Cox" at Feb 16, 2003 05:22:18 AM X-Mailer: ELM [version 2.5 PL6] 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: 1129 Lines: 36 > > > Why can't we have a mailing list that sends out a diff for each > > > update? > > > > You can, just get Linus to add a trigger to his tree to do so. > > He did, the list exists 8) I thought so: http://marc.theaimsgroup.com/?l=linux-kernel&m=104534718212591&w=2 I just wanted to confirm that bk-commit-head is actually: 1. Complete 2. Realtime If so, anybody can track Linus' tree, in real time, without using BitKeeper. Therefore, mailing lists for every single Linux-related BK repository would allow anybody to track all of the trees in real time, without using BK. Unless bandwidth is a problem, (possible for dial-up users), I don't see why we can't do that. How many people subscribed to this list are still on dial-up? Larry needn't even pay for the outbound bandwidth for the mailing list, except to forward it to somebody who is willing to send it out. John. - 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/