That's really weird! Thank anyway for the effort. Did you found anything so bad that sounds like a blocking point? Would eventually be possible to proceed with this patch set and amend the text later or do you suggest to wait?
Regards Antonio On Mon, Mar 8, 2021, 13:11 Tommy Murphy <[email protected]> wrote: > Hi Antonio > > Unfortunately, I was about 75% of the way through my review comments when > I got this and lost everything and I don't have time right now to redo > them... :-| > > > > Cheers > Tommy > > ------------------------------ > *From:* Antonio Borneo <[email protected]> > *Sent:* Sunday 7 March 2021 22:14 > *To:* OpenOCD <[email protected]> > *Subject:* [OpenOCD-devel] Request for review - licenses and SPDX > > Hi all, > > I would like to merge the changes to switch openocd licensing tag to > SPDX, but I have not received 'enough' feedback/review. > > The first question is if you agree on the licensing switch itself. > > Then, most of these changes are just moving/adding license files taken > from the FSF. Nothing to review there! > But I have added two important files! > My second question is about the 'wording' I have used in these files. > I'm not a native English speaker nor a lawyer, so your review there is > more than welcome. > The two files are: > - The final text in file 'COPYING' > http://openocd.zylin.com/gitweb?p=openocd.git;f=COPYING;h=0e8db929e671 > - The new text in file 'LICENSES/license-rules.txt' (partially copied > from Linux kernel) > http://openocd.zylin.com/#/c/5973/3/LICENSES/license-rules.txt > > For your reference, the whole patch set is here: > http://openocd.zylin.com/#/q/topic:spdx > > Thanks, > Antonio > > > _______________________________________________ > OpenOCD-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/openocd-devel >
_______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
