From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 24 Aug 2001 13:20:43 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 24 Aug 2001 13:20:33 -0400 Received: from mx5.port.ru ([194.67.57.15]:15108 "EHLO mx5.port.ru") by vger.kernel.org with ESMTP id ; Fri, 24 Aug 2001 13:20:21 -0400 From: "Samium Gromoff" <_deepfire@mail.ru> To: Florian.Weimer@RUS.Uni-Stuttgart.DE Cc: linux-kernel@vger.kernel.org Subject: Re: source control? Mime-Version: 1.0 X-Mailer: mPOP Web-Mail 2.19 X-Originating-IP: [195.34.27.172] Reply-To: "Samium Gromoff" <_deepfire@mail.ru> Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Message-Id: Date: Fri, 24 Aug 2001 21:20:34 +0400 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > > That's a great description of all source control! "Makes it all to easy > > for other people to push crap into your tree"! > Try Aegis. It enforces a develop/review/integrate cycle for each > change. and slows down the things... and hides (though not completely) the process from the people... one-thread-modify of some piece of code is inefficeient. When X code hacker splits his changes on small pieces and feeds them to Linus^WSourceControl, does he need to move each of his patches thru these develop/review/integrate cycles? --- cheers, Samium Gromoff