From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753277AbXDKQfi (ORCPT ); Wed, 11 Apr 2007 12:35:38 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753278AbXDKQfi (ORCPT ); Wed, 11 Apr 2007 12:35:38 -0400 Received: from mx01.qsc.de ([213.148.129.14]:37389 "EHLO mx01.qsc.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753277AbXDKQfh convert rfc822-to-8bit (ORCPT ); Wed, 11 Apr 2007 12:35:37 -0400 From: Rene Rebe Organization: ExactCODE To: Adrian Bunk Subject: Re: Linux 2.6.16.47-rc1 Date: Wed, 11 Apr 2007 18:34:32 +0200 User-Agent: KMail/1.9.6 Cc: linux-kernel@vger.kernel.org References: <20070411141408.GC10141@stusta.de> In-Reply-To: <20070411141408.GC10141@stusta.de> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8BIT Content-Disposition: inline Message-Id: <200704111834.32705.rene@exactcode.de> X-Spam-Score: -1.4 (-) X-Spam-Report: Spam detection software, running on the system "grum.localhost", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Hi Adrian, first front off: thanks for the phantastic 2.6.16 stable maintenance. Currently I wonder if you have any plan for doing the 2.6.16 review for let's say "years", or if you "soon" pick some new series such as 2.6.20 or so for long-term maintenance. [...] Content analysis details: (-1.4 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.4 ALL_TRUSTED Passed through trusted hosts only via SMTP Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi Adrian, first front off: thanks for the phantastic 2.6.16 stable maintenance. Currently I wonder if you have any plan for doing the 2.6.16 review for let's say "years", or if you "soon" pick some new series such as 2.6.20 or so for long-term maintenance. I ask because I wonder if I should wait a bit with a production 2.6.17 kernel line I maintain right now for just one installation base, if you choose some 2.6.2x I can hop on, or whether it is wiser to just downdate this series and profit from the "long-term" 2.6.16 maintenance that is no fun to replicate for 2.6.17 just for this one install pool ... Thanks in advance, -- René Rebe - ExactCODE GmbH - Europe, Germany, Berlin http://exactcode.de | http://t2-project.org | http://rene.rebe.name +49 (0)30 / 255 897 45