From: Martin Michlmayr <tbm@cyrius.com>
To: linux-mips@linux-mips.org
Subject: Re: -stable branches usage
Date: Mon, 11 Jun 2007 13:17:08 +0200 [thread overview]
Message-ID: <20070611111708.GA12814@deprecation.cyrius.com> (raw)
In-Reply-To: <20070529130833.GA4334@linux-mips.org>
* Ralf Baechle <ralf@linux-mips.org> [2007-05-29 14:08]:
> It's probably not a surprise when I'm saying that maintaining all
> the -stable branches of 2.6.16..2.6.21 for MIPS is a major effort
> and increasingly simply a huge pain in the ... you know where due
> to the differences. So before I actually deciede when and which of
> the branches I'm going to dump I would like to poll who actually
> uses these -stable branches.
For Debian, the 2.6.18 tree is useful since our stable kernel is based
on that release. However, we can only put crucial fixes into a stable
release, so I wouldn't expect much to show up on the 2.6.18 branch.
--
Martin Michlmayr
http://www.cyrius.com/
prev parent reply other threads:[~2007-06-11 11:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 13:08 -stable branches usage Ralf Baechle
2007-06-11 11:17 ` Martin Michlmayr [this message]
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=20070611111708.GA12814@deprecation.cyrius.com \
--to=tbm@cyrius.com \
--cc=linux-mips@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox