Return-Path: <linux-kernel-owner+willy=40w.ods.org@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S265320AbTBOWAT>; Sat, 15 Feb 2003 17:00:19 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S265333AbTBOWAT>; Sat, 15 Feb 2003 17:00:19 -0500
Received: from [81.2.122.30] ([81.2.122.30]:9222 "EHLO darkstar.example.net")
	by vger.kernel.org with ESMTP id <S265320AbTBOWAR>;
	Sat, 15 Feb 2003 17:00:17 -0500
From: John Bradford <john@grabjohn.com>
Message-Id: <200302152211.h1FMBK6a001200@darkstar.example.net>
Subject: Re: openbkweb-0.0
To: lm@bitmover.com (Larry McVoy)
Date: Sat, 15 Feb 2003 22:11:20 +0000 (GMT)
Cc: linux-kernel@vger.kernel.org
In-Reply-To: <20030215215259.GA22512@work.bitmover.com> from "Larry McVoy" at Feb 15, 2003 01:52:59 PM
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: 890
Lines: 21

Larry,

>From reading this thread, and the similar ones that have preceeded it,
it seems to me that most people are not exactly bothered about using
the SCM functionality of BitKeeper, but just want to get the
up-to-the-second changes to Linus' tree.

I always thought that that is what the bk-commit mailing lists were
for?  I could be wrong about that, not having used BitKeeper - if so,
what are they for, and would it not be possible to simply have a
mailing list which got sent a diff every time Linus' updated his tree?

Then people could just filter the mail from that list in to a script
that patched their local copy of the tree.

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/