Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Alfred M. Szmidt" <ams@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: pedro@codesourcery.com, gdb-patches@sourceware.org, 	msnyder@vmware.com
Subject: Re: [RFC] what should we do about COPYING?
Date: Sun, 20 Dec 2009 12:33:00 -0000	[thread overview]
Message-ID: <E1NMKyT-00067a-VV@fencepost.gnu.org> (raw)
In-Reply-To: <20091220122013.GF2788@adacore.com> (message from Joel Brobecker 	on Sun, 20 Dec 2009 16:20:13 +0400)


   > Also, in gdb/ it appears some new gplv2 or later files have crept
   > in:

   Fixed most of them.  I haven't had time to look at gpl.texi yet, so
   I have no idea what this file is used for yet.  I suspect that we
   should have updated that file too.p

It is used to show the license conditions of GDB in the manual.


  reply	other threads:[~2009-12-20 12:33 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 [this message]
2009-12-20 14:27       ` Stan Shebs
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=E1NMKyT-00067a-VV@fencepost.gnu.org \
    --to=ams@gnu.org \
    --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