From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Arnez <arnez@linux.vnet.ibm.com>
Cc: palves@redhat.com, brobecker@adacore.com, gdb@sourceware.org
Subject: Re: SVG version of GDB mascot (archer fish)
Date: Fri, 29 Sep 2017 18:13:00 -0000 [thread overview]
Message-ID: <83shf55q5x.fsf@gnu.org> (raw)
In-Reply-To: <m31smpqv79.fsf@oc1027705133.ibm.com> (message from Andreas Arnez on Fri, 29 Sep 2017 19:19:06 +0200)
> From: Andreas Arnez <arnez@linux.vnet.ibm.com>
> Cc: palves@redhat.com, brobecker@adacore.com, gdb@sourceware.org
> Date: Fri, 29 Sep 2017 19:19:06 +0200
>
> > FWIW, https://www.gnu.org/licenses/license-list.en.html#OtherLicenses
> > only mentions CC BY-SA 4.0, so I think we should first find out
> > whether version 3.0 is GPL-compatible.
>
> Hm, if I understand the license terms of CC BY-SA 3.0 US correctly, I
> should be able to upgrade the license of my derivative work to CC BY-SA
> 4.0. Sounds like that would be preferable?
I think so, yes. If nothing else, it will allow us to avoid asking
the FSF lawyers about this.
next prev parent reply other threads:[~2017-09-29 18:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 17:04 Andreas Arnez
2017-09-25 22:28 ` Joel Brobecker
2017-09-25 23:12 ` Pedro Alves
2017-09-26 11:36 ` Andreas Arnez
2017-09-26 11:46 ` Pedro Alves
2017-09-26 12:06 ` Andreas Arnez
2017-09-26 13:16 ` Pedro Alves
2017-09-29 12:41 ` Eli Zaretskii
2017-09-29 17:19 ` Andreas Arnez
2017-09-29 18:13 ` Eli Zaretskii [this message]
2017-10-04 13:30 ` Andreas Arnez
2017-10-04 14:08 ` Pedro Alves
2017-10-04 14:45 ` Eli Zaretskii
2017-10-04 14:48 ` Pedro Alves
2017-10-04 16:56 ` Eli Zaretskii
2017-10-06 9:17 ` Andreas Arnez
2017-09-26 11:40 ` Andreas Arnez
2017-09-26 12:40 ` Joel Brobecker
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=83shf55q5x.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=arnez@linux.vnet.ibm.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=palves@redhat.com \
/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