On Thu, 20 Apr 2017 09:28:59 +0200,
Ludwig Nussel wrote:
Looking at https://build.opensuse.org/request/show/488903
whether there is actually any value in having each and every git
commit mentioned in the .changes files?
Would it make sense to e.g. only list the range of commits that was
added, plus any bug, fate, cve etc entries fixed in that range?
Well, I understand your surprise, but it's really the result of our
own changes. SLE/Leap kernel takes our patches, thus each of these
changes should be recorded. Actually, the upstream stable change is a
single, relatively small changelog entry. All the rest are about our
own backports and fixes. These own changes are just so big.
You can see the difference by comparing with TW kernel changelog. TW
kernel mostly follows the upstream with far less own patches, thus the
changelog is much smaller.
OTOH, for SLE/Leap, we are responsible for each of our own changes.
And customers often require to take a look through the changes without
git accesses. Thus, not only bug#/CVE#, but each detailed change is
good to have as a changelog record.
Last but not least, the kernel package is constantly updated. So we
can't group the git commits in the changelog -- as changelog is
supposed to be incremental.
Of course, if you have a better idea to shorten the log, please let us
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org