Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 7 Mar 2002 18:53:35 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 7 Mar 2002 18:53:14 -0500 Received: from austin.greshamstorage.com ([216.143.252.250]:36364 "EHLO austin.openmic.com") by vger.kernel.org with ESMTP id ; Thu, 7 Mar 2002 18:53:08 -0500 Message-ID: <3C87FD12.8060800@greshamstorage.com> Date: Thu, 07 Mar 2002 17:51:46 -0600 From: "Jonathan A. George" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8+) Gecko/20020226 MIME-Version: 1.0 To: linux-kernel@vger.kernel.org Subject: Kernel SCM: When does CVS fall down where it REALLY matters? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org I am considering adding some enhancements to CVS to address deficiencies which adversely affect my productivity. Since it would obviously be nice to have a completely free (or even GPL :-) tool which is not considered to consist of unacceptable compromises in the process of kernel development I would like to know what the Bitkeeper users consider the minimum acceptable set of improvements that CVS would require for broader acceptance. Obviously the tremendous set of features that Bitkeeper has are nice, but I'd like to narrow the comparative flaws to a manageable set. Any comments would benefit all of the free SCM projects by at least helping to provide a guiding light. --Jonathan-- - 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/