From: Jonathan Nieder <jrnieder@gmail.com>
To: David Kastrup <dak@gnu.org>
Cc: git@vger.kernel.org
Subject: Re: A few contributor's questions
Date: Fri, 31 Jan 2014 08:19:24 -0800 [thread overview]
Message-ID: <20140131161924.GA4332@google.com> (raw)
In-Reply-To: <8738k44808.fsf@fencepost.gnu.org>
Hi,
David Kastrup wrote:
> builtin/blame.c merely states
>
> /*
> * Blame
> *
> * Copyright (c) 2006, Junio C Hamano
> */
I think you planned to make substantial changes, so
> /*
> * Blame
> *
> * Copyright (c) 2006--2014, Junio C Hamano and others
> * Licensed under GPLv2. See Git's COPYING file for details.
> */
towards the end of the series (or squashed into some patch that makes
significant changes) looks fine to me.
Also keep in mind that you don't need a copyright notice to own
copyright, that it would be crazy for someone to claim you've assigned
copyright on your changes without an explicit reassignment, and that
libgit2's git.git-authors file that keeps coming up includes a comment
with a heuristic for delving into the history to find the authors of
some code.
[...]
> Permissable-Licenses: GPL Version 2 or later
Wouldn't a signed message on your website or some other public place
(e.g., the mailing list) do the trick?
Or a sentence in a commit message saying
"I'd be happy to have these changes relicensed under the GPL version 2
or later."
sounds fine to me, at least.
Thanks and hope that helps,
Jonathan
next prev parent reply other threads:[~2014-01-31 16:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 13:04 A few contributor's questions David Kastrup
2014-01-31 16:19 ` Jonathan Nieder [this message]
2014-01-31 17:00 ` David Kastrup
2014-01-31 18:48 ` Jonathan Nieder
2014-01-31 21:06 ` David Kastrup
2014-01-31 23:58 ` David Lang
2014-02-03 16:35 ` Andreas Ericsson
2014-02-03 17:35 ` David Kastrup
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=20140131161924.GA4332@google.com \
--to=jrnieder@gmail.com \
--cc=dak@gnu.org \
--cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.