From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932267AbWFLXcA (ORCPT ); Mon, 12 Jun 2006 19:32:00 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932462AbWFLXcA (ORCPT ); Mon, 12 Jun 2006 19:32:00 -0400 Received: from server99.tchmachines.com ([72.9.230.178]:21385 "EHLO server99.tchmachines.com") by vger.kernel.org with ESMTP id S932267AbWFLXcA (ORCPT ); Mon, 12 Jun 2006 19:32:00 -0400 Date: Mon, 12 Jun 2006 16:33:31 -0700 From: Ravikiran G Thirumalai To: Andi Kleen Cc: discuss@x86-64.org, linux-kernel@vger.kernel.org Subject: Re: [discuss] x86_64: x86-64 mailing lists / posting patchkits / x86-64 releases Message-ID: <20060612233331.GA3924@localhost.localdomain> References: <200606121307.54556.ak@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200606121307.54556.ak@suse.de> User-Agent: Mutt/1.4.2.1i X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - server99.tchmachines.com X-AntiAbuse: Original Domain - vger.kernel.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - scalex86.org X-Source: X-Source-Args: X-Source-Dir: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 12, 2006 at 01:07:54PM +0200, Andi Kleen wrote: > > Hallo, > > Some administrativa. > > In the last time I've posted all patches I sent to Linus > at discuss@x86-64.org at least once. I did this because this list is relatively > low volume and I tended to get some useful feedback from the people > subscribed here. > > However I heard some rumours that I scared people away > from the list with the many patches. > > I also planned to post patches more often to get better > turnaround for reviews on changed patches. > > We still have a patches@x86-64 mailing list on x86-64.org which > is mostly unused. If I moved the big patch floods over there, > would the people who do reviews subscribe there? Please comment. Given a choice I prefer one list for patches and discussion. Patches on a separate list will eventually result in discussions of those patches on that list, and might even leave out interested parties out of the ensuing discussion. My 2c; If a separate patch list is needed for staging patches to mainline, it could be something like mm-commits - a broadcast only list by the maintainer. Thanks, Kiran