Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nathanael Nerode <neroden@twcny.rr.com>
To: gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com,
	binutils@sources.redhat.com
Subject: [patch] copyright notice correction on libiberty/make-relative-prefix.c
Date: Sat, 24 May 2003 16:08:00 -0000	[thread overview]
Message-ID: <20030524160827.GA432@doctormoo> (raw)

This file came out of GCC (it was split off of gcc.c).  The current copyright
terms are not acceptable since they don't actually give a copyright for the
file.  Accordingly I propose this change, which I believe is a correction
and accurately represents which project one needs a copyright assignment
for to edit this file.

Only edits in CVS history are by drow, dannysmith, and nickc (and the
latter two are miniscule, probably not copyrightable).

	* make-relative-prefix.c: Fix license statement.

Index: make-relative-prefix.c
===================================================================
RCS file: /cvs/gcc/gcc/libiberty/make-relative-prefix.c,v
retrieving revision 1.4
diff -u -r1.4 make-relative-prefix.c
--- make-relative-prefix.c	20 Feb 2003 22:10:58 -0000	1.4
+++ make-relative-prefix.c	24 May 2003 16:02:59 -0000
@@ -2,7 +2,7 @@
    Copyright (C) 1987, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
    1999, 2000, 2001, 2002 Free Software Foundation, Inc.
 
-This file is part of libiberty.
+This file is part of GCC.
 
 GCC is free software; you can redistribute it and/or modify it under
 the terms of the GNU General Public License as published by the Free


             reply	other threads:[~2003-05-24 16:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-24 16:08 Nathanael Nerode [this message]
2003-05-25 15:49 ` DJ Delorie

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=20030524160827.GA432@doctormoo \
    --to=neroden@twcny.rr.com \
    --cc=binutils@sources.redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sources.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