From: ludo@gnu.org (Ludovic Courtès)
To: Jason Self <jason@bluehome.net>
Cc: bug-guix@gnu.org
Subject: Re: Add GNU fdisk
Date: Tue, 27 Nov 2012 21:18:24 +0100 [thread overview]
Message-ID: <87pq2yg5pr.fsf@gnu.org> (raw)
In-Reply-To: <1354043747.17765@bluehome.net> (Jason Self's message of "Tue, 27 Nov 2012 11:15:48 -0800 (PST)")
Hi,
"Jason Self" <jason@bluehome.net> skribis:
> Ludovic Courtès said:
>> Yes, I’ve been wondering too. The thing is, while most are purely
>> declarative like this, some, like those in base.scm, are trickier
>> and definitely copyrightable. In base.scm, the composition of
>> packages in the bootstrap phase may also be copyrightable in itself.
>
> I suppose that there's no harm in adding one, then. Even if it should
> turn out that it's not copyrightable an invalid copyright notice
> wouldn't cause any harm in this case.
Yes.
Nikita Karetnikov <nikita.karetnikov@gmail.com> skribis:
> So, what's the policy on copyright statements?
>
> I'm not a lawyer that's why I think that it's better to be safe than
> sorry (i.e. to use a copyright statement).
Agreed. So the policy is unchanged: each file must contain a copyright
statement.
Thanks,
Ludo’.
prev parent reply other threads:[~2012-11-27 20:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-25 22:25 Add GNU fdisk Jason Self
2012-11-26 0:07 ` Ludovic Courtès
2012-11-26 13:35 ` Nikita Karetnikov
2012-11-26 16:23 ` Ludovic Courtès
2012-11-26 18:47 ` Jason Self
2012-11-26 20:22 ` Ludovic Courtès
2012-11-27 18:29 ` Nikita Karetnikov
2012-11-27 19:15 ` Jason Self
2012-11-27 20:18 ` Ludovic Courtès [this message]
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pq2yg5pr.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-guix@gnu.org \
--cc=jason@bluehome.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).