From: Michael Haggerty <mhagger@alum.mit.edu>
To: Andy Parkins <andyparkins@gmail.com>
Cc: git discussion list <git@vger.kernel.org>,
Michiel Holtkamp <notifications@github.com>,
mhagger/git-multimail
<reply+i-10159725-60cb2c338c594bd09d77fe2f8d628aa55114a3f6-119718@reply.github.com>
Subject: Re: [git-multimail] License unknown (#1)
Date: Wed, 13 Feb 2013 13:10:26 +0100 [thread overview]
Message-ID: <511B82B2.8030803@alum.mit.edu> (raw)
In-Reply-To: <201302121528.07961.andyparkins@gmail.com>
On 02/12/2013 04:28 PM, Andy Parkins wrote:
> On Sunday 27 January 2013 18:52:58 Michael Haggerty wrote:
>> I have a question about the license of contrib/hooks/post-commit-email.
>> [...]
>
> Keeping up with the git mailing list got a bit much, [...]
Very understandable :-)
> My apologies to everyone; I've been lax supporting the script -- I never
> really expected it to be as widely used as it has been, I was always expecting
> someone would come along and replace it so I'm pleased that Michael has done
> so (although it's a little disheartening to read of it being called "hacky",
> when I tried very hard to make it as clear and modular as I could).
FWIW I think the script was quite well-structured (within the
limitations of shell scripting anyway) and I had no problem
understanding it and translating it to Python.
>> If somebody can explain what license the code is under and how they come
>> to that conclusion, I would be very grateful.
>>
>> And if Andy Parkins (the original author) is listening, please indicate
>> whether you had any intent *other* than GPLv2.
>
> I intended it to be under the same license as Git. I had read in one of the
> patch submission files (which I can't seem to find now) that all submissions
> were considered part of git.
Thanks. Given that you submitted the original version under GPLv2, and
later contributors certainly had no reason to assume any *other*
license, I think any reasonable person will be satisfied that the whole
script in its current form is under GPLv2.
> If an explicit declaration is needed, I am happy to give it. Let me know what
> form this should take and I'll supply it.
Personally, I am satisfied by your email statement. I will leave the
derived work, git-multimail, also under GPLv2. Assuming that
git-multimail supersedes yours, its explicit choice of license will make
the situation clear for future users.
Thanks!
Michael
--
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
prev parent reply other threads:[~2013-02-13 12:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mhagger/git-multimail/issues/1@github.com>
[not found] ` <mhagger/git-multimail/issues/1/12754195@github.com>
2013-01-27 18:52 ` [git-multimail] License unknown (#1) Michael Haggerty
[not found] ` <511A04DA.7010809@alum.mit.edu>
2013-02-12 15:11 ` Fwd: " Andy Parkins
2013-02-12 15:28 ` Andy Parkins
2013-02-13 12:10 ` Michael Haggerty [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=511B82B2.8030803@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=notifications@github.com \
--cc=reply+i-10159725-60cb2c338c594bd09d77fe2f8d628aa55114a3f6-119718@reply.github.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 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.