|
From: Mark W. <ma...@kl...> - 2025-10-12 23:03:50
|
Hi, We discussed this on this list, with the core valgrind developers and the FSF Licensing and Compliance Lab what the correct way was to do this. The patch itself is a little too big to post to the list, but you can see it here: https://code.wildebeest.org/git/user/mjw/valgrind/log/?h=gplv3 There are two patches, one cleanup: Update where to get a copy of the GNU General Public License Several files still said to write to the Free Software Foundation at a particular address. Add a reference to <http://www.gnu.org/licenses/> instead. Some files that were imported into valgrind from other places still mention the old address. They should be updated when new versions get imported. And the actual update: Upgrade to GNU General Public License version 3 - Update COPYING and VEX/LICENSE.GPL to version 3. - Update README, NEWS, docs/manual license and contributing text. - Update file headers to say either version 3 of the License, or (at your option) any later version. - Leave tests and perf file headers as is, unless the code is derived from Valgrind/VEX. - Leave valgrind.h, cachegrind.h, callgrind.h, drd.h, helgrind.h, memcheck.h and dhat.h Hybrid-BSD licensed. I like to merge these on Friday (Oct 17) before releasing 3.26.0-RC1. Please let me know if you have any questions or concerns about this update. Thanks, Mark |