Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <chastain@cygnus.com>
To: chastain@cygnus.com, gdb-patches@sources.redhat.com, kevinb@cygnus.com
Subject: Re: [PATCH RFC] Update/correct copyright notices
Date: Wed, 28 Feb 2001 15:26:00 -0000	[thread overview]
Message-ID: <200102282326.PAA06715@bosch.cygnus.com> (raw)

Hi Kevin,

Most people think of this stuff as comments.  I think of it as declarative
statements in Legalese.  The actual execution of Legalese in a court of
law is very rare, but when it does happen, the stakes are high.  Hence
I proofread.

> But in each case, the ChangeLog files are in error.

OK.  Andrew, what would you like to do about this?  Would you like patches
for ChangeLog files?

> diff -upr gdb.orig/thread.c gdb/thread.c
> --- gdb.orig/thread.c	Mon Jan 29 17:06:26 2001
> +++ gdb/thread.c	Wed Feb 28 15:03:34 2001
> @@ -1,8 +1,9 @@
>  /* Multi-process/thread control for GDB, the GNU debugger.
> -   Copyright 1986, 1987, 1988, 1993, 1998, 1999, 2000, 2001
> -
> -   Contributed by Lynx Real-Time Systems, Inc.  Los Gatos, CA.
> +   Copyright 1986, 1987, 1988, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
> +   2000, 2001
>     Free Software Foundation, Inc.
> +   Contributed by Lynx Real-Time Systems, Inc.  Los Gatos, CA.
> +   

I request that the head maintainer verify the copyright assignment 
for gdb/thread.c.
 
> Yes, the use of ``*'' as a filename wildcard in ChangeLog entries is
> really quite annoying.  There were also entries that said foo.[hc] or
> sometimes {foo,bar}.c (or sometimes a combination of the two), but I
> was able to handle these cases.

How about a note in CONTRIBUTE forbidding wildcards and glob patterns
in ChangeLog entries?

Michael


             reply	other threads:[~2001-02-28 15:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-28 15:26 Michael Elizabeth Chastain [this message]
2001-02-28 15:47 ` Stan Shebs
  -- strict thread matches above, loose matches on Subject: below --
2001-02-28 16:47 Michael Elizabeth Chastain
2001-02-28 16:36 Michael Elizabeth Chastain
2001-02-28 16:42 ` Kevin Buettner
2001-02-28  9:12 Michael Elizabeth Chastain
2001-02-28  9:02 Michael Elizabeth Chastain
2001-02-28  9:22 ` Kevin Buettner
2001-02-28  8:56 Michael Elizabeth Chastain
2001-02-28 14:56 ` Kevin Buettner
2001-02-28 16:24   ` Kevin Buettner
2001-03-01  0:33   ` Eli Zaretskii
2001-03-01  1:19     ` Kevin Buettner
2001-03-01  3:13       ` Eli Zaretskii
2001-02-28  0:42 Kevin Buettner
2001-02-28  0:50 ` Kevin Buettner
2001-02-28  3:20   ` Eli Zaretskii
2001-02-28  7:45     ` Andrew Cagney
2001-02-28  3:18 ` Eli Zaretskii
2001-02-28  8:52   ` Andrew Cagney
2001-02-28  9:20   ` Kevin Buettner
2001-02-28 11:11     ` Eli Zaretskii
2001-02-28 17:31 ` Andrew Cagney

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=200102282326.PAA06715@bosch.cygnus.com \
    --to=chastain@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kevinb@cygnus.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