From: Michael Haggerty <mhagger@alum.mit.edu>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
Simon P <simon.git@le-huit.fr>
Cc: git@vger.kernel.org
Subject: Re: [git-multimail] smtplib, check certificate
Date: Fri, 22 Apr 2016 08:41:36 +0200 [thread overview]
Message-ID: <5719C7A0.50403@alum.mit.edu> (raw)
In-Reply-To: <vpqoa92rxew.fsf@anie.imag.fr>
On 04/22/2016 08:05 AM, Matthieu Moy wrote:
> Simon P <simon.git@le-huit.fr> writes:
> > This patch is inspired from
> >
> > https://github.com/graingert/secure-smtplib/blob/master/src/secure_smtplib/__init__.py
>
> Please, add your sign-off and a proper commit message to your patch,
> see:
>
> https://github.com/git-multimail/git-multimail/blob/master/CONTRIBUTING.rst
I hate that we even have to worry about this stuff, but
graingert/secure-smtplib looks to be GPLv3, whereas git-multimail is
GPLv2 (like the Git project and Linux); *not* "GPLv2 or later". So if
"inspired" means "incorporated copyrightable content" then this patch
might be problematic.
Michael
next prev parent reply other threads:[~2016-04-22 6:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 21:44 [git-multimail] smtplib, check certificate Simon P
2016-04-22 6:05 ` Matthieu Moy
2016-04-22 6:41 ` Michael Haggerty [this message]
2016-04-24 19:14 ` Simon Pontié
2016-04-24 18:20 ` Simon Pontié
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=5719C7A0.50403@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=simon.git@le-huit.fr \
/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).