On Thu, 26 Aug 2004 21:00:54 +0200 Philippe Bertin wrote: | 'Llo All, | | I've read some theory about the kernel, and some year ago I've been busy | digging into the internals of the USB kernel working (since then, I'm | sure I've already forgotten a lot). But I did not go into setting up a | working environment aiming at tracking several concurrent versions at | that time. | | Now I want to gradually work me in (again, but this time more | structured) into the USB- sources of the Linux kernel, actually with the | 'hope' I'll eventually be able to contribute to the sources. | | As a first step, I'd like to be able to keep track of several kernel | versions (the backported one, the new one, and maybe more ?), as I have | noticed before that it frequently occured that patches were sent against | different versions. | | So I realize I now should first organize my things. But the question is: | HOW ? | | - How does one keep track of these different versions ? Does on HAVE to | use bitkeeper ? Or can one also do it with CVS (I'm more familiar with CVS)
Some (several, lots of?) people like BK very much, but no, it's not required, although depending on what you are doing, it might make your work easier. | - does there exist a CVS tree downloadable somewhere ? There's a bkcvs (bk -> cvs, i.e., updated from BK) available via rsync at: rsync://rsync.kernel.org/pub/scm/linux/kernel/bkcvs/ | - where are the *very* latest sources located exactly ? In a BK tree that is viewable at http://linux.bkbits.net:8080/linux-2.5 or pullable (clonable) from bk://linux.bkbits.net:8080/linux-2.5, and put into tarballs (full kernel tarballs as in linux-x.y.z.tar.bz2 and updates for -rc versions, -bk snapshots, etc.) at http://www.kernel.org/pub/linux/kernel/v2.6/ with -rc's here: http://www.kernel.org/pub/linux/kernel/v2.6/testing/ and bk nightly snapshots (updates) here: http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/ | I am sure the same helpful people are still around. If anyone of you | would give me a starting point, I'd be very thankful. There are also a bunch of scripts that are handy for maintaining kernel patches. See 'quilt' (search for it at freshmeat.net) or (it's parent) 'patch-scripts' at http://www.zip.com.au/~akpm/linux/patches/patch-scripts-0.18/ Also 'wiggle' (google for it) will try to merge patches that 'patch' fails on. In the kernel tree, there is scripts/patch-kernel to update a kernel tree in place with whatever version you want. Or there is 'ketchup' (http://www.selenic.com/ketchup/) to download and apply any of a large set of well-known patches (like -mm, -rc, -bk). So that gives you a lot of alternatives. The question/problem is what is it that you are trying to maintain? Several versions of a full kernel? I'd probably use BK for that. Patches for one driver, for multiple kernel versions? Personally I think that BK is overkill for that, but others may prefer to use it. I would just use patch-scripts (or quilt) to maintain patches, and ketchup to download & apply updates. -- ~Randy ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
