Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [rfa:threads] Report when using libthread_db
Date: Tue, 05 Aug 2003 19:51:00 -0000	[thread overview]
Message-ID: <200308051951.h75JpIa6028849@duracef.shout.net> (raw)

> Should the "Loading" message come after the (C) notice, or the (C) put 
> before the modules are initialized?

I am not a lawyer, but ... the legal requirement is that copyright
notices appear in a prominent place.  I don't think it has to be the
very first thing printed, it just has to be prominent.  I think the idea
is that if someone copies it without your permission, and then they
claim "I didn't notice that you copyrighted it!", then you would say
"any half-awake person would have seen my copyright notice WHILE THEY
WERE COPYING THE REST OF MY WORK!"

If you look at a book, the copyright notice isn't on the cover.
But it's close to the front.

There might be a GNU coding standard about it though.

Michael C


             reply	other threads:[~2003-08-05 19:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-05 19:51 Michael Elizabeth Chastain [this message]
2003-08-05 20:10 ` Elena Zannoni
  -- strict thread matches above, loose matches on Subject: below --
2003-09-08  3:05 Michael Elizabeth Chastain
2003-09-08 13:21 ` Andrew Cagney
2003-09-08  2:28 Michael Elizabeth Chastain
2003-09-08  3:01 ` Daniel Jacobowitz
2003-09-09 14:29 ` Elena Zannoni
2003-08-23  1:49 Michael Elizabeth Chastain
2003-09-04 17:24 ` Andrew Cagney
2003-09-05 15:42 ` Elena Zannoni
2003-08-22 19:40 Michael Elizabeth Chastain
2003-08-08 15:51 Michael Elizabeth Chastain
2003-08-05 19:26 Andrew Cagney
2003-08-07 19:57 ` Andrew Cagney
     [not found]   ` <mailpost.1060286286.1556@news-sj1-1>
2003-08-07 20:31     ` cgd
2003-08-08 14:51       ` Andrew Cagney
2003-08-21 22:10         ` Andrew Cagney
2003-08-21 22:47           ` Mark Kettenis

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=200308051951.h75JpIa6028849@duracef.shout.net \
    --to=mec@shout.net \
    --cc=ac131313@redhat.com \
    --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