From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: GPLv3: copying.awk needs to be adjusted
Date: Sat, 18 Aug 2007 02:44:00 -0000 [thread overview]
Message-ID: <20070818024200.GD24165@adacore.com> (raw)
There is one thing I haven't done yet, with respect to the transition
to GPLv3: The license printed by GDB when using the "show/info copying"
and "show/info warranty" should be extracted from the COPYING3 files,
not COPYING.
So the associated copying.c rule in Makefile.in needs to be adjusted.
But this is not all: Because the license has changed, the awk script
needs to be adjusted as well. In particular, the awk script is splitting
the contents of the license into two parts: the "copying" part, and
the "warranty" part. With GPLv2, it was using "NO WARRANTY" as the
marker. We need to change it to use "15. Disclaimer of Warranty.".
I tried that, but somehow it failed miseraly.
I've just spent several hours working on this switch and I'm overdosing.
I'll leave that for later unless some good soul takes care of it for me
first.
--
Joel
next reply other threads:[~2007-08-18 2:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-18 2:44 Joel Brobecker [this message]
2007-08-18 9:27 ` Andreas Schwab
2007-08-19 4:55 ` Joel Brobecker
2007-08-19 8:07 ` Andreas Schwab
2007-08-21 13:44 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070818024200.GD24165@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox