From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: keep a gen 2013 snapshot on mirrors
Date: Fri, 15 Nov 2013 15:24:46 +0000 (UTC) [thread overview]
Message-ID: <pan$e878f$3bb7140$83f95437$d286a06c@cox.net> (raw)
In-Reply-To: CAGfcS_kv_nMfPFKRWUYh8DBkRry1rPEPovPi1VGV6jet=Q7Bhw@mail.gmail.com
Rich Freeman posted on Fri, 15 Nov 2013 08:38:20 -0500 as excerpted:
> 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.
I can (cautiously) agree with that, tho I'm sure there are those who
would take an opposing position, certainly if they're lawyers paid to do
so!
Meanwhile, I found your (paraphrased) "on the third line, after the
comma" example interesting, both since I saw a similar argument on one of
the pages that came up in my google, and because it's basically what a sed
script (as opposed to a patch) does in practice. The point being that
simple instructions saying /how/ to do it, without incorporating any of
the original work, can hardly be said to be derived.
(The example I saw in my google was text instructions for cutting a face
out of a larger photo and putting a red frame around it. It's quite
clear that those text instructions are not derivative of a particular
photo, while a screen-grab illustrating the process may well be
considered derivative of the original photo, since it includes part of
it. A sed script is arguably similar, tho s// regex replacement can
certainly be borderline, but for the triviality test.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2013-11-15 15:25 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
2013-11-15 15:24 ` Duncan [this message]
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='pan$e878f$3bb7140$83f95437$d286a06c@cox.net' \
--to=1i5t5.duncan@cox.net \
--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