public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: "hlidea(注意力集中)" <hlidea.gm@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Where can I find old bluetooth kernel patches?
Date: Mon, 02 Mar 2009 09:07:11 +0100	[thread overview]
Message-ID: <1235981231.6074.65.camel@localhost.localdomain> (raw)
In-Reply-To: <c89fa46a0903012233t16c5c453qa98441b51d28ba15@mail.gmail.com>

Hi Chris,

we don't top post on this mailing list. Don't do that again since I am
really good at ignoring emails like that.

> I suggest you keep the old patches on the Internet. These patches are
> valueable especially for some embedded linux system. You know, upgrade
> the kernel on embedded system is not easy, so I think you can just
> leave the old patches there without any support for them.
> Most people will benefit from these old patches.Thanks a lot.

Actually putting up these patches would slow down the progress. Nobody
should be using a 2.4 kernel anymore. The 2.4 series is now since 5
years in maintenance mode. My tolerance level is currently at 2.6.25
kernel and everything before is just an ancient kernel and you should
not use it. If you do then you are on your own and please don't bother
anybody in the open source community with these kind of silly requests.
Please think about what you are asking from the community. What does the
BlueZ community would get in return for giving you these patches?

Regards

Marcel



      reply	other threads:[~2009-03-02  8:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-26  8:29 Where can I find old bluetooth kernel patches? hlidea(注意力集中)
2009-02-28 21:47 ` Marcel Holtmann
2009-03-02  6:33   ` hlidea(注意力集中)
2009-03-02  8:07     ` Marcel Holtmann [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=1235981231.6074.65.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=hlidea.gm@gmail.com \
    --cc=linux-bluetooth@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox