Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262272AbVDGJT5 (ORCPT ); Thu, 7 Apr 2005 05:19:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262400AbVDGJT5 (ORCPT ); Thu, 7 Apr 2005 05:19:57 -0400 Received: from ozlabs.org ([203.10.76.45]:52716 "EHLO ozlabs.org") by vger.kernel.org with ESMTP id S262272AbVDGJT4 (ORCPT ); Thu, 7 Apr 2005 05:19:56 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16980.64324.87931.513333@cargo.ozlabs.ibm.com> Date: Thu, 7 Apr 2005 19:20:04 +1000 From: Paul Mackerras To: Andrew Morton Cc: David Woodhouse , torvalds@osdl.org, linux-kernel@vger.kernel.org Subject: Re: Kernel SCM saga.. In-Reply-To: <20050407015019.4563afe0.akpm@osdl.org> References: <1112858331.6924.17.camel@localhost.localdomain> <20050407015019.4563afe0.akpm@osdl.org> X-Mailer: VM 7.19 under Emacs 21.4.1 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 950 Lines: 23 Andrew Morton writes: > The problem with those is letting other people get access to it. I guess > that could be fixed with a bit of scripting and rsyncing. Yes. > (I don't do that for -mm because -mm basically doesn't work for 99% of the > time. Takes 4-5 hours to out a release out assuming that nothing's busted, > and usually something is). With -mm we get those nice little automatic emails saying you've put the patch into -mm, which removes one of the main reasons for wanting to be able to get an up-to-date image of your tree. The other reason, of course, is to be able to see if a patch I'm about to send conflicts with something you have already taken, and rebase it if necessary. Paul. - 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/