All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Hans Verkuil" <hverkuil@xs4all.nl>
To: "Trent Piepho" <xyzzy@speakeasy.org>
Cc: "Mauro Carvalho Chehab" <mchehab@infradead.org>,
	"Devin Heitmueller" <devin.heitmueller@gmail.com>,
	"Hans Werner" <hwerner4@gmx.de>,
	linux-media@vger.kernel.org
Subject: Re: Results of the 'dropping support for kernels <2.6.22' poll
Date: Tue, 24 Mar 2009 13:25:23 +0100 (CET)	[thread overview]
Message-ID: <63406.62.70.2.252.1237897523.squirrel@webmail.xs4all.nl> (raw)


> On Sat, 21 Mar 2009, Mauro Carvalho Chehab wrote:
>> > When this thread was started, it was about dropping support for
>> > kernels < 2.6.22.  However, it has turned into a thread about moving
>> > to git and dropping support for *all* kernels less than the bleeding
>> > edge -rc candidate (only supporting them through a backport system for
>> > testers).  The two are very different things.
>
> Yes they are very different things.  I do not like a poll about dropping
> the current build system being disguised as a poll about dropping support
> for very old kernels.  How about a new poll, "should developers be
> required
> to have multiple systems and spend the majority of their time recompiling
> new kernels and testing nvidia and wireless drivers?"

The poll was just about dropping support for old kernels. Nothing more,
nothing less. There were a few who commented that they wouldn't mind
dropping all compatibility, but those were very much a minority. I for one
want to keep the compatibility code in one way or another so we can
support the last X kernels and make life easy for ourselves and for our
users.

Regards,

       Hans

-- 
Hans Verkuil - video4linux developer - sponsored by TANDBERG


             reply	other threads:[~2009-03-24 12:25 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-24 12:25 Hans Verkuil [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-03-02 21:18 Results of the 'dropping support for kernels <2.6.22' poll Hans Verkuil
2009-03-02 22:46 ` kilgota
2009-03-02 23:28   ` Simon Kenyon
2009-03-02 22:47 ` Trent Piepho
2009-03-03  7:19   ` Hans Verkuil
2009-03-03  8:06     ` Trent Piepho
2009-03-04 17:17 ` Mauro Carvalho Chehab
2009-03-05 18:56   ` Guennadi Liakhovetski
2009-03-05 20:19     ` Trent Piepho
2009-03-05 20:36       ` Guennadi Liakhovetski
2009-03-05 20:57         ` Trent Piepho
2009-03-05 21:29           ` Hans Verkuil
2009-03-05 22:20           ` Guennadi Liakhovetski
2009-03-07  0:01             ` Trent Piepho
2009-03-07  0:46               ` Guennadi Liakhovetski
2009-03-07  1:46                 ` hermann pitton
2009-03-15 16:39                 ` Trent Piepho
2009-03-15 16:48                   ` Hans Verkuil
2009-03-19  9:10                     ` Trent Piepho
2009-03-15 19:00                   ` Devin Heitmueller
2009-03-07 21:12               ` Adam Baker
2009-03-20 20:47   ` Hans Werner
2009-03-20 22:20     ` Mauro Carvalho Chehab
2009-03-21  2:03       ` Devin Heitmueller
2009-03-21  3:04         ` Mauro Carvalho Chehab
2009-03-21  5:21           ` Trent Piepho
2009-03-21 12:05           ` Devin Heitmueller
2009-03-21 17:35             ` Mauro Carvalho Chehab
2009-03-24 12:04               ` Trent Piepho
2009-03-21  5:16         ` Trent Piepho

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=63406.62.70.2.252.1237897523.squirrel@webmail.xs4all.nl \
    --to=hverkuil@xs4all.nl \
    --cc=devin.heitmueller@gmail.com \
    --cc=hwerner4@gmx.de \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=xyzzy@speakeasy.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.