From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Re: keep a gen 2013 snapshot on mirrors
Date: Fri, 15 Nov 2013 08:38:20 -0500 [thread overview]
Message-ID: <CAGfcS_kv_nMfPFKRWUYh8DBkRry1rPEPovPi1VGV6jet=Q7Bhw@mail.gmail.com> (raw)
In-Reply-To: <pan$3e108$fd2e402e$e53a6146$e354bb8@cox.net>
On Fri, Nov 15, 2013 at 8:17 AM, Duncan <1i5t5.duncan@cox.net> wrote:
> To the extent patches are larger than the rather blurry "trivial" level,
> I believe there's no question that they ARE derivative. In the case of
> literal patches, literally and provably so, due to the context-diff which
> literally includes lines from the original from which it is derived.
Ok, to illustrate, let's consider the bit I just quoted the original
work. This would be a derivative work:
To the extent patches are larger than the rather blurry "trivial" level,
I believe there's no question that they ARE derivative. In the case of
literal patches, literally, and figuratively, and provably so, due to
the context-diff which
literally includes lines from the original from which it is derived.
This would not be a derivative work:
and figuratively,
This isn't a derivative work:
On line three insert the characters "and figuratively, " after the second comma.
This is more fuzzy, but is probably fair use to the extent that it is
a derivative work:
I believe there's no question that they ARE derivative. In the case of
-literal patches, literally, and provably so, due to the context-diff which
+literal patches, literally, and figuratively, and provably so, due to
the context-diff which
literally includes lines from the original from which it is derived.
That's what I'm getting at. The actual changes themselves aren't a
derivative work - it is the result of applying them that is.
Rich
next prev parent reply other threads:[~2013-11-15 13:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 18:58 [gentoo-dev] keep a gen 2013 snapshot on mirrors Francesco R.
2013-11-13 19:12 ` Rich Freeman
2013-11-13 20:49 ` Roy Bamford
2013-11-13 21:18 ` Rich Freeman
2013-11-15 13:17 ` [gentoo-dev] " Duncan
2013-11-15 13:38 ` Rich Freeman [this message]
2013-11-15 15:24 ` Duncan
2013-11-15 15:59 ` Peter Stuge
2013-11-14 0:27 ` [gentoo-dev] " Tom Wijsman
2013-11-14 13:17 ` Francesco R.
2013-11-14 14:01 ` Rich Freeman
2013-11-14 13:19 ` Lars Wendler
2013-11-14 19:49 ` Ian Stakenvicius
2013-11-13 19:16 ` Rick "Zero_Chaos" Farina
2013-11-14 4:38 ` Johann Schmitz
2013-11-14 13:09 ` Francesco R.
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='CAGfcS_kv_nMfPFKRWUYh8DBkRry1rPEPovPi1VGV6jet=Q7Bhw@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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