[qt/qt/qtqa]: Summary of bulk changes made

KDE Git Services - Bulk Change <[email protected]>
Newsgroups gmane.comp.kde.cvs
Message-ID <[email protected]>
Git repository change summary for qt/qt/qtqa
Pushed by mirror-service into branch 'dev'.
Changed from b5085c396f1801a8c862cf3dc4b14ce2ff996583 to 679f874965069490b25d3b84cb0077ff743b1568
Acknowledgement was received that this change introduces only existing code that has been pushed to another public open source repository.

This change contains the following new commits:

Git commit 679f874965069490b25d3b84cb0077ff743b1568 by Edward Welbourne on 31/07/2026 at 08:51..
Allow Qt-Security headers to not immediately follow SPDX ones

Amends commit 5c055d0719a984b6db92f1b77ba299508960883d (6.11).
QUIP 23 says

  The Qt-Security comment line must be located towards the beginning
  of the file, before any source code. By preference it's usually
  placed right after the SPDX license header.

I'd coded resetboring.py's Selector.__end_copyright() on the
assumption that it always followed SPDX, as preferred by the QUIP, but
we have at least one family of generated files where it's landed after
the "edits to this will be lost next time it's regenerated" warning
comment. (I suspect it was put there by a script that just looked for
the first blank line after the SPDX headers.)

This change allows that the end of what's understood to be the
copyright header may change significantly between versions (to include
whatever lies between the SPDX line and the Qt-Security line). Since
this necessarily makes the first hunk of the diff an addition, with no
change on the old side, but a position on the old side it considers to
be after the end of its copyright header, allow an empty old side to
count as before the end of its copyright header when the new side is
before its.

Pick-to: 6.12
Change-Id: I2c3eb18b0c8a554ffeb0d421b4f5134d005b3d64
Reviewed-by: Kai Köhne <[email protected]>
https://invent.kde.org/qt/qt/qtqa/-/commit/679f874965069490b25d3b84cb0077ff743b1568
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.