Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger via Gdb-patches <gdb-patches@sourceware.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC PATCH] sim: switch Cygnus Solutions copyrights to FSF
Date: Thu, 13 Jan 2022 15:50:04 -0500	[thread overview]
Message-ID: <YeCQfJOZiH8V3yqi@vapier> (raw)
In-Reply-To: <YdlNCnTmH/X9w8lz@adacore.com>

[-- Attachment #1: Type: text/plain, Size: 986 bytes --]

On 08 Jan 2022 12:36, Joel Brobecker wrote:
> > This was done for the vast majority of files in the sim tree, but looks
> > like these few were missed.  While Cygnus Solutions doesn't exist today,
> > it merged with RedHat who has FSF assignment in place.
> 
> I would ask the copyright clerk at the FSF (copyright-clerk@fsf.org)
> about that. Intuitively, even though Cygnus has been merged into
> RedHat, and RedHat has a copyright assignment on file for *past*
> and future changes, I don't know that it means *any* past changes
> contributed by an entity which became part of RH after the change
> was contributed can see its copyright be re-assigned. I'm wondering
> if someone at RedHat must give permission or rather express the
> desire to assign this code's copyright to the FSF?

thanks, i'll reach out to the FSF.  these old copyrights are annoying
because it's easy to miss when refactoring or writing new code when the
rest of the code base is FSF.
-mike

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2022-01-13 20:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-01 18:41 Mike Frysinger via Gdb-patches
2022-01-08  8:36 ` Joel Brobecker via Gdb-patches
2022-01-13 20:50   ` Mike Frysinger via Gdb-patches [this message]

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=YeCQfJOZiH8V3yqi@vapier \
    --to=gdb-patches@sourceware.org \
    --cc=brobecker@adacore.com \
    --cc=vapier@gentoo.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