From: Mark H Weaver <mhw@netris.org>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: No copyright notice on gen-scmconfig.c
Date: Sat, 02 Feb 2013 09:05:05 -0500 [thread overview]
Message-ID: <87k3qqbylq.fsf@tines.lan> (raw)
In-Reply-To: <87halv7ynw.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sat, 02 Feb 2013 12:17:23 +0100")
ludo@gnu.org (Ludovic Courtès) writes:
> Mark H Weaver <mhw@netris.org> skribis:
>
>> Is there a reason why gen-scmconfig.c lacks a copyright notice?
>
> Not that I know of. Probably a mistake.
Should we add one? The commit logs show that gen-scmconfig.c has been
modified in every year between 2003 and 2013. Given that, should we put
"Copyright (C) 2003-2013 Free Software Foundation, Inc." in that file?
Mark
next prev parent reply other threads:[~2013-02-02 14:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-02 8:48 No copyright notice on gen-scmconfig.c Mark H Weaver
2013-02-02 11:17 ` Ludovic Courtès
2013-02-02 14:05 ` Mark H Weaver [this message]
2013-02-02 14:35 ` Ludovic Courtès
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k3qqbylq.fsf@tines.lan \
--to=mhw@netris.org \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).