Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 14 Oct 2002 19:48:21 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 14 Oct 2002 19:48:21 -0400 Received: from e5.ny.us.ibm.com ([32.97.182.105]:63915 "EHLO e5.ny.us.ibm.com") by vger.kernel.org with ESMTP id ; Mon, 14 Oct 2002 19:48:20 -0400 Importance: Normal Sensitivity: Subject: Re: [Evms-devel] Re: Linux v2.5.42 To: Alexander Viro Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com, evms-devel@lists.sourceforge.net X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Mark Peloquin" Date: Mon, 14 Oct 2002 18:57:05 -0500 X-MIMETrack: Serialize by Router on D01ML072/01/M/IBM(Release 5.0.11 |July 29, 2002) at 10/14/2002 07:53:20 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1074 Lines: 31 On 10/14/2002 at 05:57 PM, Alexander Viro wrote: > As for the bugs getting fixed, one of the main problems with EVMS merge > now is that it (as any merge) shifts part of that very burden from EVMS > maintainers to other developers *and* *it* *shifts* *too* *much*. > That's what "ready to be merged" boils down to. It's a question of how > many problems will be inflicted by the merge upon current and future > development - over all kernel. AFAICS in its current state EVMS is not > ready. And yes, it means that EVMS maintainers get to play catch up for > a while. We don't want to shift the burden of EVMS onto other developers. We are willing to play catch up for a while, however the feature-freeze date is looming. > Nobody refuses to help them, BTW. Can you identify areas you feel need special attention? Mark - 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/