Mark Post wrote: > Ummm, no. When you unpack linux-2.6.5-s390-04-april2004.tar.gz, you get two > files, linux-2.6.5-s390-04-april2004.diff, and .readme.
Well, yes, but that is the *full* patch. Specifically in order to make back-and-forth porting easier, however, we always provide a *per-problem* (or per-feature as may be) break-up of the big patch into multiple small patches. This can be downloaded by clicking on the *second* 'Download' button; the one with 'per problem' next to it (as I wrote below). > Moreover, there is no way to look at the 47,000 lines of patches in those > files and determine which lines belong to > The kerntypes patch > The multicast notifier patch > The zfcp module_exit vs. lun/port object kfree patch > The shared-IPv6-card patch > The lost-dirty-bit fix Very true; and indeed exactly the reason why we provide per-problem patches ;-) > I just want some way of checking which version of a source code module is > considered by the developers to be current. From there, I can figure out > what the 2.6.7 (or whatever) version is supposed to look like when I'm done. > I don't need to see IBM OCO code, or unreleased features, etc., etc. The 'current' version is the one in Linus' current Bitkeeper head. > If things are to the point where it is feasible (and you make it sound like > it is), I think it may be time to start publishing patch sets against what > ever version is current from kernel.org, and not keep putting them out > against 2.6.5 (or what ever milestone release has been set). _That_ would > make things a lot easier. Our current procedure is to produce patches against Bitkeeper head (ready for inclusion), and backport them (if appropriate) to apply against our developerWorks service stream. We do not generate additional backports against other official kernel releases, because that would be a lot of additional work. Either use the service stream, wait for inclusion in the next official release, or backport yourself ... Bye, Ulrich -- Dr. Ulrich Weigand [EMAIL PROTECTED] ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
