From: Jonathan Nieder <jrnieder@gmail.com>
To: David Kastrup <dak@gnu.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/2] Two janitorial patches for builtin/blame.c
Date: Tue, 21 Jan 2014 08:55:46 -0800 [thread overview]
Message-ID: <20140121165546.GE18964@google.com> (raw)
In-Reply-To: <87d2jlqp7x.fsf@fencepost.gnu.org>
David Kastrup wrote:
> Now I might have sent at an unopportune time: blame.c is mostly
> attributed to Junio who seems to have been a few days absent now.
>
> I also have seen quite a few mails and patch submissions on the list go
> basically unanswered in the last few days.
In the U.S., yesterday was a federal holiday (Martin Luther King, Jr.
day) and the two days before were the weekend.
[...]
> maintained indefinitely and may be redistributed consistent with
> this project or the open source license(s) involved.
>
> Now the file involved (builtin/blame.c) itself does not state _any_
> license.
Most of git is GPLv2-only. (As an aside, if there's interest then I'd
be happy to see most of it change to GPLv2-or-later since that makes
it possible to link to code under the Apache License. But I'm also
happy with the status quo.)
[...]
> As far as I am concerned, I am willing to license my work under the
> GPLv2 or any later version at the discretion of whoever wants to work
> with it. I think that should be compatible with the project goals.
>
> Now the above passage states "you might note so in your copyright
> message", but my patches do not even contain a copyright message and it
> is not clear to me that they should, or that there is a sensible place
> to place such "copyright messages".
Yeah, since these patches aren't adding a large new chunk of code
there's no need for a new copyright notice and so no place to put that
kind of thing unless Junio wants to relicense blame (which would be
orthogonal to these patches).
Thanks and hope that helps,
Jonathan
next prev parent reply other threads:[~2014-01-21 16:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-19 18:57 [PATCH 0/2] Two janitorial patches for builtin/blame.c David Kastrup
2014-01-19 18:57 ` [PATCH 1/2] builtin/blame.c: struct blame_entry does not need a prev link David Kastrup
2014-01-21 21:54 ` Junio C Hamano
2014-01-21 23:02 ` David Kastrup
2014-01-19 18:57 ` [PATCH 2/2] Eliminate same_suspect function in builtin/blame.c David Kastrup
2014-01-21 16:22 ` [PATCH 0/2] Two janitorial patches for builtin/blame.c David Kastrup
2014-01-21 16:55 ` Jonathan Nieder [this message]
2014-01-21 17:40 ` David Kastrup
2014-01-21 17:44 ` Jonathan Nieder
2014-01-21 17:58 ` David Kastrup
2014-01-21 19:15 ` Jonathan Nieder
2014-01-21 19:56 ` David Kastrup
2014-01-21 20:01 ` Jonathan Nieder
2014-01-21 21:30 ` David Kastrup
2014-01-21 20:20 ` Junio C Hamano
2014-01-21 22:56 ` David Kastrup
2014-01-21 19:53 ` Jonathan Nieder
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=20140121165546.GE18964@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 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 NNTP newsgroup(s).