From: Christopher Li <sparse@chrisli.org>
To: Dan Carpenter <error27@gmail.com>
Cc: Josh Triplett <josh@joshtriplett.org>, linux-sparse@vger.kernel.org
Subject: Re: relicensing Sparse
Date: Thu, 11 Aug 2011 15:47:26 -0700 [thread overview]
Message-ID: <CANeU7QmUmMKy4ohZuZ41njgBhW5_7qoqyjFPW6aqBYf1dBNAZQ@mail.gmail.com> (raw)
In-Reply-To: <20110811103908.GI3777@shale.localdomain>
On Thu, Aug 11, 2011 at 3:39 AM, Dan Carpenter <error27@gmail.com> wrote:
> Most of the people who I missed would have been filtered out anyway
> by my ten lines of code minimum contribution requirement. Perhaps I
> should just contact everyone.
>
> I looked at how Mozilla did the relicensing and they pretty much went
> by who had their name in a copyright notice at the top of the file.
> For files without a copyright notice they looked at the history. So
> it seems like tiny contributions were ignored.
>
> I'm obviously not a lawyer. Contacting everyone is probably doable
> if that's what you think is best.
I agree try to contact every one is about the license change is better.
How many people have you contact and how many reply have you got
so far?
Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-08-11 22:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 22:08 relicensing Sparse Dan Carpenter
2011-08-10 23:09 ` Josh Triplett
2011-08-11 10:39 ` Dan Carpenter
2011-08-11 20:49 ` Josh Triplett
2011-08-11 22:47 ` Christopher Li [this message]
2011-08-11 22:52 ` Dan Carpenter
[not found] <20110226173414.GN18043@bicker>
2011-02-26 18:10 ` Alexey Dobriyan
2011-02-26 18:24 ` Dan Carpenter
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=CANeU7QmUmMKy4ohZuZ41njgBhW5_7qoqyjFPW6aqBYf1dBNAZQ@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=error27@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-sparse@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.