All of lore.kernel.org
 help / color / mirror / Atom feed
From: hermann pitton <hermann-pitton@arcor.de>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Trent Piepho <xyzzy@speakeasy.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	Hans Verkuil <hverkuil@xs4all.nl>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Jean Delvare <khali@linux-fr.org>
Subject: Re: Results of the 'dropping support for kernels <2.6.22' poll
Date: Sat, 07 Mar 2009 02:46:22 +0100	[thread overview]
Message-ID: <1236390382.2259.17.camel@pc09.localdom.local> (raw)
In-Reply-To: <Pine.LNX.4.64.0903070144520.5665@axis700.grange>

Hi,

Am Samstag, den 07.03.2009, 01:46 +0100 schrieb Guennadi Liakhovetski:
> On Fri, 6 Mar 2009, Trent Piepho wrote:
> 
> > On Thu, 5 Mar 2009, Guennadi Liakhovetski wrote:
> > > On Thu, 5 Mar 2009, Trent Piepho wrote:
> > > > ALSA used a partial tree, but their system was much worse than v4l-dvb's.
> > > > I think the reason more systems don't do it is that setting up the build
> > > > system we have with v4l-dvb was a lot of work.  They don't have that.
> > >
> > > Right, it was a lot of work, it is still quite a bit of work (well, I'm
> > > not doing that work directly, but it affetcs me too, when I have to adjust
> > > patches, that I generated from a complete kernel tree to fit
> > > compatibility-"emhanced" versions), and it is not going to be less work.
> > 
> > Why must you generate your patches from a different tree?  One could just
> > as well say that the linux kernel indentation style is more work, since
> > they use GNU style have to translate their patch from a re-indented tree.
> 
> [snip]
> 
> Hans has already answered your question very well in this thread. I don't 
> think I can add anything.
> 
> Thanks
> Guennadi

for me Trent clearly has the better arguments, but I do have of course a
different point of view.

Let's have this embedded Linux conference and listen to the arguments we
hopefully get some links to.

There is a lot going on, but you must convince me at least to buy some
of this stuff I call gadgets. I don't see any need so far ;)

You likely can get still anybody seriously interested to build the
always next rc1 and then one close to the final next kernel release too,
but I seriously doubt that you can convince anybody at all to give up
totally what we have for embedded mixed trees fun on latest git and
break all others by will for your latest pleasure.

Cheers,
Hermann





  reply	other threads:[~2009-03-07  1:44 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
2009-03-24 12:25 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=1236390382.2259.17.camel@pc09.localdom.local \
    --to=hermann-pitton@arcor.de \
    --cc=g.liakhovetski@gmx.de \
    --cc=hverkuil@xs4all.nl \
    --cc=khali@linux-fr.org \
    --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.