From: "Hans Werner" <HWerner4@gmx.de>
To: hverkuil@xs4all.nl
Cc: linux-media@vger.kernel.org
Subject: Re: POLL: for/against dropping support for kernels < 2.6.22
Date: Wed, 25 Feb 2009 20:10:01 +0100 [thread overview]
Message-ID: <20090225191001.50400@gmx.net> (raw)
In-Reply-To: <49A586CE.7030600@gmx.de>
> Should we drop support for kernels <2.6.22 in our v4l-dvb repository?
>
> _: Yes
> _: No
>
>
YES (but I would go even further)
>
> Optional question:
>
> Why:
>
The aim should be to bring improvements to the released Linux kernel.
The *only* point relevant for both development and testing is the current
latest development kernel, currently 2.6.29-rc6.
So I would go further : development should be moved to git and support
for all previous kernels should be dropped allowing concentration of
development resources on making patches which will be applied to the head
of the git tree.
I think it is completely wrong-headed to have "v4l-dvb" as a thing which
can be installed on top of old kernels to add new driver support to old
kernels. It is a waste of time to create such a thing, and a drain on
resources to support.
As for users/testers, the message should be made crystal clear: if you
want to try running bleeding-edge code to get the latest support your
hardware the first thing to do is upgrade to the latest kernel. It will
be easier to communicate with developers who are (or should be!) working
on improving the latest development kernel.
This is better for everyone : time wasted on backporting and talking
about/debugging old kernel issues will be eliminated and drivers will
released in the mainline kernels faster.
It will also clarify to distros and users where the "coal face" is:
new hardware support comes from new kernels, not v4l-dvb or (usually)
backports or anything else.
Fixes for bugs in last stable kernel (currently 2.6.28.7) should be
pushed in if known, but never new features.
Distros or those with special commercial reasons can work on backports
if they really feel they can justify the use of their time, money and
other resources. They are also the only ones who can properly take account
of all the userland consequences of making a backport because they see
the whole system.
Regards,
Hans
--
Release early, release often.
Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01
next prev parent reply other threads:[~2009-02-25 19:10 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-22 10:15 POLL: for/against dropping support for kernels < 2.6.22 Hans Verkuil
2009-02-22 19:12 ` CityK
2009-02-22 23:52 ` Andy Walls
2009-02-23 4:28 ` [Bulk] " CityK
2009-02-22 22:56 ` Guennadi Liakhovetski
2009-02-22 23:27 ` kilgota
2009-02-23 1:13 ` hermann pitton
2009-02-23 6:41 ` Robert Golding
2009-02-23 8:32 ` VDR User
2009-02-23 12:26 ` Mauro Carvalho Chehab
2009-02-23 14:54 ` Mauro Carvalho Chehab
2009-02-23 14:48 ` Douglas Schilling Landgraf
2009-02-23 14:53 ` David Ellingsworth
2009-02-24 5:04 ` Trent Piepho
2009-02-24 7:25 ` Hans Verkuil
2009-02-24 13:12 ` Ales Jurik
2009-02-24 20:19 ` Hans Verkuil
2009-02-24 20:43 ` Jonathan Johnson
2009-02-25 0:06 ` Markus Rechberger
2009-02-25 3:24 ` Markus Rechberger
2009-02-25 0:01 ` Simeon Simeonov
2009-02-24 20:40 ` Rudy Zijlstra
2009-02-24 21:02 ` Michael Krufky
2009-02-24 23:37 ` hermann pitton
2009-02-25 0:52 ` Ant
2009-02-25 8:23 ` Simon Kenyon
2009-02-25 12:31 ` Simon Kenyon
2009-02-25 17:58 ` wk
2009-02-25 18:19 ` Jean-Francois Moine
2009-02-25 19:10 ` Hans Werner [this message]
2009-02-25 19:32 ` Lars Hanisch
2009-02-26 5:26 ` Mike Isely
2009-02-27 2:25 ` Magnus Damm
2009-03-01 19:51 ` Tobias Stoeber
2009-03-01 21:50 ` Adrian Pardini
-- strict thread matches above, loose matches on Subject: below --
2009-02-23 1:24 sonofzev
2009-02-23 13:49 Jean Delvare
2009-02-23 13:54 ` Trent Piepho
2009-02-24 11:56 ` John Pilkington
2009-02-24 20:41 ` Simon Kenyon
[not found] ` <49A3DDFC.6010608@tesco.net>
2009-02-24 13:15 ` Jean Delvare
2009-02-24 14:34 ` John Pilkington
2009-02-23 14:09 Hans Verkuil
2009-02-25 8:35 Hans Verkuil
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=20090225191001.50400@gmx.net \
--to=hwerner4@gmx.de \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@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