From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail.gmx.net ([213.165.64.20]:56818 "HELO mail.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1753405AbZCES4Z (ORCPT ); Thu, 5 Mar 2009 13:56:25 -0500 Date: Thu, 5 Mar 2009 19:56:37 +0100 (CET) From: Guennadi Liakhovetski To: Mauro Carvalho Chehab cc: Hans Verkuil , linux-media@vger.kernel.org, Jean Delvare Subject: Re: Results of the 'dropping support for kernels <2.6.22' poll In-Reply-To: <20090304141715.0a1af14d@pedra.chehab.org> Message-ID: References: <200903022218.24259.hverkuil@xs4all.nl> <20090304141715.0a1af14d@pedra.chehab.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-media-owner@vger.kernel.org List-ID: On Wed, 4 Mar 2009, Mauro Carvalho Chehab wrote: > Beside the fact that we don't need to strip support for legacy kernels, the > advantage of using this method is that we can evolute to a new development > model. As several developers already required, we should really use the > standard -git tree as everybody's else. This will simplify a lot the way we > work, and give us more agility to send patches upstream. > > With this backport script, plus the current v4l-dvb building systems, and after > having all backport rules properly mapped, we can generate a "test tree" > based on -git drivers/media, for the users to test the drivers against their > kernels, and still use a clean tree for development. Sorry, switching to git is great, but just to make sure I understood you right: by "-git drivers/media" you don't mean it is going to be a git tree of only drivers/media, but it is going to be a normal complete Linux kernel tree, right? Thanks Guennadi --- Guennadi Liakhovetski, Ph.D. Freelance Open-Source Software Developer