Patrick Boettcher wrote: > Hi Johannes, > > On Sat, 2 Jul 2005, Johannes Stezenbach wrote: > >> C.Y.M wrote: >> >>> Is the policy going to be that the cvs of the dvb-kernel should be in >>> sync with >>> current kernel release candidate (from kernel.org)? >>> >>> I am using 2.6.13-rc1 with cvs, and just wanted to make sure these >>> changes work >>> with 2.6.12? >> >> >> As was discussed one or two months ago I'm going to maintain >> a patch for users against the latest release: >> http://linuxtv.org/downloads/patches/2.6.12/ >> >> For development CVS should work with latest -rc. >> >> I considered adding some temporary #if KERNEL_VERSION, >> they are not difficult to remove when creating patches >> for lkml. But they make it much harder to feed back >> changes from the kernel into CVS, so I'd like to avoid it. > > > Hmm, I cannot update my kernel every two weeks. But I understand your > maintaining-problems. > > Up to now all patches from -rc's have been compatible with the current > stable kernel version, but this time it doesn't even compile anymore... > > I won't be able to test my latest changes, without undoing the recent > rc-compatibility changes. > > I don't know if it will be a problem for the other developers, but for > me it is one. > > Can you suggest me something handy for getting along with it, without > going to 2.6.VV-rcX ? (VV > my current kernel-version)? > I posted a patch yesterday that would fix your build problem with 2.6.12 and current cvs if you reversed it. See thread "[linux-dvb] CVS and 2.6.13-rc1 don't compil". Regards, C.
