Messages in this thread | | | Date | Wed, 14 May 1997 22:56:46 +0200 | From | Andries.Brouwer@cwi ... | Subject | Re: Documentation/Changes update for 2.0.3x |
| |
From jlewis@inorganic5.fdt.net Wed May 14 20:22:03 1997
On Wed, 14 May 1997 Andries.Brouwer@cwi.nl wrote:
> [Besides: what is the function of these `Changes'?
I guess that's really the question.
> To tell us what the most recent version of some software is? > I don't think so. It should tell us what the oldest version > of the software is that still will work without problems > with this new kernel.]
Personally, I like to have the very latest non-broken version, rather than the oldest one that still works. If I'm going to bother to go get the source and compile stuff, getting the very latest usable version hopefully delays having to repeat that excercise.
Of course - but the past year there have been over twenty versions of mount, each only infinitesimally different from the previous one. Upgrading to the very latest is meaningless, unless either you are upgrading anyway, or you have a problem and want to see whether it has been fixed in the latest release.
So, all these small improvements should not be listed in the `Changes' file - that would only cause needless effort for people who believe that they must have all versions mentioned before they can use this new kernel. But for example the recent NFS code in 2.1.32 and later requires a new mount, so at that point Changes should mention that 2.6g is required.
And when you go to this site and find that in fact later versions than mentioned do exist, well, then you pick the latest version present and the version mentioned (as a fall-back, just to be sure).
Andries
| |