Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <stan@codesourcery.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Pedro Alves <pedro@codesourcery.com>,
	gdb-patches@sourceware.org,   Michael Snyder <msnyder@vmware.com>
Subject: Re: [RFC] what should we do about COPYING?
Date: Sun, 20 Dec 2009 14:27:00 -0000	[thread overview]
Message-ID: <4B2E3440.7070609@codesourcery.com> (raw)
In-Reply-To: <20091220122013.GF2788@adacore.com>

Joel Brobecker wrote:
>> Note that there is code in sim that is v2 or later, copyrighted Andrew
>> Cagney, not FSF.
>>     
>
> I wonder why this code is copyrighted Cagney and not the FSF, since
> I thought that one requirement for pushing to the FSF tree was
> assigning your changes to the FSF. Not sure what to do next...
>   
Back then, simulators in GDB were still somewhat of a novel concept, and 
we waffled about whether to officially consider them part of GDB, or as 
a separate library that happened to be linked in - the simulator could 
always be built as its own program, and GDB could be built without 
simulator. Plus at the time we really really really wanted a PPC 
simulator. :-)
> Regardless, there is a COPYING at the root of the sources, so perhaps
> we can rely on version 2 of the license being available there.
>   
That's good enough for me,  in general people expect that foo/COPYING 
applies to everything in that directory and its subdirs, but not to 
sibling dirs.

Stan


  parent reply	other threads:[~2009-12-20 14:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-18  7:33 Joel Brobecker
2009-12-18 15:52 ` Stan Shebs
2009-12-18 17:36 ` Michael Snyder
2009-12-18 17:43   ` Pedro Alves
2009-12-20 12:20     ` Joel Brobecker
2009-12-20 12:33       ` Alfred M. Szmidt
2009-12-20 14:27       ` Stan Shebs [this message]
2009-12-21  7:55         ` 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=4B2E3440.7070609@codesourcery.com \
    --to=stan@codesourcery.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=pedro@codesourcery.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