Suraj, please don't send me copies of messages to the mailing list;
http://www.debian.org/MailingLists/#codeofconduct>.
"Suraj N. Kurapati" <[EMAIL PROTECTED]> writes:
> Ben Finney wrote:
> > The set of permissions you receive is the *intersection* of the
> > permissions granted by all licenses t
Suraj N. Kurapati wrote:
> Ben Finney wrote:
> > The set of permissions you receive is the *intersection* of the
> > permissions granted by all licenses to the work (as modified by
> > rights you have regardless of license under copyright law). You
> > may only exercise those permissions that rema
Ben Finney wrote:
> The set of permissions you receive is the *intersection* of the
> permissions granted by all licenses to the work (as modified by
> rights you have regardless of license under copyright law). You
> may only exercise those permissions that remain.
>
> The set of restrictions yo
"Suraj N. Kurapati" <[EMAIL PROTECTED]> writes:
> 3. When you modify a contained item, your modifications become
> licensed under the contained item's license.
>
> For example, when I modify mit.c, my modifications become pulled
> under the MIT license. Since the MIT license allows me to add more
Suraj N. Kurapati wrote:
> 3. When you modify a contained item, your modifications become
> licensed under the contained item's license.
Your first two points are correct, but this one is not.
You have *no right* to modify someone else's item except if the
license on that item permits it. And then
Joe Smith wrote:
> "Suraj N. Kurapati" wrote:
>> So when I appended bsd.c to mit.c, did the entire mit.c become
>> licensed under both licenses? That is, did the originally-MIT
>> portions of mit.c inherit the extra condition from the BSD
>> license?
>
> That is an easy way to view it. Technica
6 matches
Mail list logo
