All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Rebe <rene@exactcode.de>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.16.47-rc1
Date: Wed, 11 Apr 2007 18:34:32 +0200	[thread overview]
Message-ID: <200704111834.32705.rene@exactcode.de> (raw)
In-Reply-To: <20070411141408.GC10141@stusta.de>

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

  reply	other threads:[~2007-04-11 16:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-11 14:14 Linux 2.6.16.47-rc1 Adrian Bunk
2007-04-11 16:34 ` Rene Rebe [this message]
2007-04-11 18:01   ` Adrian Bunk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200704111834.32705.rene@exactcode.de \
    --to=rene@exactcode.de \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.