Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Michael Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PING/rfa/testsuite/threads] schedlock.c: add copyright notice
Date: Wed, 25 Aug 2004 23:11:00 -0000	[thread overview]
Message-ID: <412D1C8C.5080809@redhat.com> (raw)
In-Reply-To: <412B6AD9.nailILO183Z9X@mindspring.com>

Michael Chastain wrote:
> Previously submitted:
> 
>   2004-07-31
>   2004-08-08
>   2004-08-16
> 
> This patch adds a copyright notice to schedlock.c.  It doesn't touch
> anything else in schedlock.c, but naturally I'm doing this because I
> want to patch schedlock.c next (so that it compiles with gcc HEAD).
> 
> Daniel Jacobowitz created schedlock.c in 2002, and the file was edited
> in 2003 but not in 2004.  Following a previous discussion with Andrew
> Cagney and Dan Berlin, I'm not including 2004 in the list of copyright
> years.
> 
> Date sources: ChangeLog and the cvs log.
> 
> Testing: I ran schedlock.exp 32 times before and after on native
> i686-pc-linux-gnu to make sure no absolute line numbers got hosed.
> 
> Okay to commit?
> 
> Michael C

Can't see any reason not to...

> 
> ===
> 
> 2004-07-31  Michael Chastain  <mec.gnu@mindspring.com>
> 
> 	* gdb.threads/schedlock.c: Add copyright notice.
> 
> Index: gdb.threads/schedlock.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/testsuite/gdb.threads/schedlock.c,v
> retrieving revision 1.3
> diff -c -3 -p -r1.3 schedlock.c
> *** gdb.threads/schedlock.c	15 Apr 2003 02:23:11 -0000	1.3
> --- gdb.threads/schedlock.c	1 Aug 2004 01:26:43 -0000
> ***************
> *** 1,3 ****
> --- 1,22 ----
> + /* This testcase is part of GDB, the GNU debugger.
> + 
> +    Copyright 2002, 2003 Free Software Foundation, Inc.
> + 
> +    This program 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 Software Foundation; either version 2 of the License, or
> +    (at your option) any later version.
> + 
> +    This program is distributed in the hope that it will be useful,
> +    but WITHOUT ANY WARRANTY; without even the implied warranty of
> +    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> +    GNU General Public License for more details.
> + 
> +    You should have received a copy of the GNU General Public License
> +    along with this program; if not, write to the Free Software
> +    Foundation, Inc., 59 Temple Place - Suite 330,
> +    Boston, MA 02111-1307, USA.  */
> + 
>   #include <stdio.h>
>   #include <unistd.h>
>   #include <stdlib.h>
> 



  reply	other threads:[~2004-08-25 23:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24 16:20 Michael Chastain
2004-08-25 23:11 ` Michael Snyder [this message]
2004-08-26 13:11   ` Michael Chastain
  -- strict thread matches above, loose matches on Subject: below --
2004-08-16 16:56 Michael Chastain
2004-08-08 22:25 Michael Chastain

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=412D1C8C.5080809@redhat.com \
    --to=msnyder@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec.gnu@mindspring.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