On Thu, Feb 14, 2008 at 11:19 AM, Sharpe, Sam J <[EMAIL PROTECTED]> wrote: > On Thu, 2008-02-14 at 10:46 -0600, inode0 wrote: > > If you actually look at the changelog you will see exactly which fixes > > went in at each level from .7 through .13 ... no gaps, no holes, no > > oops I need to rebuild this rpm. > > err, that's nice. However, if you actually *read* the changelog you > might ask: "what happened between 2.6.18-10 and 2.6.18-12... Where is > the changelog for 2.6.18-11?" or "I know what -10 fixed and I know what > -12 fixed, but what did they slip into -11 that isn't listed?" > > The point I was making is that the 53.1.13 is an RPM version number, not > related to how many issues were necessarily fixed in the kernel. I did > that by imaging a number of build steps that might be required just to > fix a single issue... > > You also provide the counter example - a single version bump contains > multiple patches and therefore fixes multiple issues.
Sam, Sorry if it sounded like I was disagreeing with you. Perhaps I misunderstood the orginal question which I thought was why are there entries in the kernel changelog for each bump from .7 through .13 but the issued errata did not mention any of those fixes except for the last one. In that context I think the answer is that .13 reverted to .6 and added the one fix that was mentioned in the issued errata for the update. So here we have an example of a bump from .6 to .13 that fixes only one issue, there are other examples of gaps without explanation, others where a bump of +.1 might fix several things, and so on. John _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
