public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: phm <moonpunter@gmail.com>
To: Milly Bitcoin <milly@bitcoins.info>,
	bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] This thread is not about the soft/hard fork technical debate
Date: Tue, 6 Oct 2015 17:14:08 -0500	[thread overview]
Message-ID: <561447B0.3030903@gmail.com> (raw)
In-Reply-To: <561360F4.2010906@bitcoins.info>


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

In any case this is basically the purpose of version tracking software
such as Git or CVS or any other. It would not be hard to figure out who
had done what. I see you're splitting hairs over nothing as usual,
though, Russ, so I'll leave you to it.

phm

Milly Bitcoin via bitcoin-dev wrote:
> Maybe you are confused with a compilation notice that would say "All Content Copyright and other rights reserved by its Respective Owners" or something similar.  That is not the same thing as claiming ownership using the "c" inside the circle. > > There is also a difference between claiming a copyright for
individual works as part of a compilation as opposed to claiming a
copyright on the compilation itself (which is what the current notice
is). > > Russ > > > On 10/6/2015 1:08 AM, Milly Bitcoin wrote: >>> The
copyright notice refers to the fact that each contributor owns >>>
copyright >>> to his own contributions. There is no legal group that
owns copyright >>> to the >>> entirety of the code. >>> >> >> No, that
is not what such a notice means.  The part after the "c" in the >>
circle is the legal owner.  If the legal owners are not properly >>
identified then the notice is not valid. >> >> --- >>  From Nolo: >> >>
What is a valid copyright notice? >> >> A copyright notice should
contain: >> •the word "copyright" >> •a "c" in a circle (©) >> •the date
of publication, and >> •the name of either the author or the owner of
all the copyright rights >> in the published work. >> >> For example,
the correct copyright for the fourth edition of The >> Copyright
Handbook, by Stephen Fishman (Nolo), is Copyright © 1998 by >> Stephen
Fishman. >> >> --- >> from USPTO: >> >> Use of the notice informs the
public that a work is protected by >> copyright, identifies the
copyright owner, and shows the year of first >> publication. >> --- >>
>> Russ >> > > > _______________________________________________ >
bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org >
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWFEewAAoJEIUV926tz9E87a4P/21Znk1tx/ZCA4eykig75S9I
d0xyLRREVL/SBOBzE8kJh1YmiHAG1ziHzsgpobNn/N2VuKanCKSXuR3niV5WRtYw
+Oa4uVZUNtAtXKSrFSiGpwJoZN5JnUADcx4sK7En3Z5gFEYSAPrMwvm+M0upl9rd
5b2/VQ/dm3fDUnntnz4DfhV3otEbcLo6imaaV6RDIPru61Fc20blHJhQPEX0laex
N1rUiUvsyUL9H66fGFYmm/6YJcO26k3gPNmmODJdApv7uTVfHBj3c2r4xKSIDVES
WxdL+DdyzJQU6Ng95793QTx29Wn8pV1FlMkC9TQ3biQ1ivoAAKbvxzI27swbPx7d
WGu/ATDj3UN2RBY3hzTTpMIVK5kITVo+QGtA8cg+KcLjVPaasYdb13zy/pE6PO8J
4AWd/nYP/bQlkrebeFylY7vQi6TNCDtpfkJE2r8H+3RovqigN+pLLVhuEVlOBtM1
7N5gAvJWqKtUIgzNKte+eS/yaOFBhHp+veC+QfNMDechC4OGM7IDVdf9oVy9DSCX
68XThI62AT+uhKjvs8ZG3L88AUiiYK6RC4YCUZVoydbQHovmvQRL3Wb36n+krcGH
iV3n3lfk7+D9IrX6ieRwmHpa9a7VAIekqUuCSBdsXBCUM5zNz48bRNJSofjWLtSm
5p0mp5jQxte8loevZztf
=psJx
-----END PGP SIGNATURE-----



  parent reply	other threads:[~2015-10-06 22:14 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-05 15:56 [bitcoin-dev] This thread is not about the soft/hard fork technical debate Sergio Demian Lerner
2015-10-05 16:39 ` NxtChg
2015-10-05 16:51 ` Luke Dashjr
2015-10-05 16:56 ` Mike Hearn
2015-10-05 17:01   ` Paul Sztorc
2015-10-05 17:33     ` Peter R
2015-10-05 17:56       ` NxtChg
2015-10-05 22:56       ` Btc Drak
2015-10-05 23:05         ` Milly Bitcoin
2015-10-05 17:35   ` Btc Drak
2015-10-06 18:23   ` Venzen Khaosan
2015-10-06 18:28     ` Venzen Khaosan
2015-10-06 19:34       ` naama.kates
2015-10-05 17:03 ` Btc Drak
2015-10-05 17:26   ` Tom Zander
2015-10-05 17:52     ` Btc Drak
2015-10-05 18:04     ` Gregory Maxwell
2015-10-05 18:33       ` Tom Zander
2015-10-05 18:50         ` NotMike Hearn
2015-10-05 17:33 ` s7r
2015-10-05 18:51   ` Tom Zander
2015-10-05 18:35 ` Gregory Maxwell
2015-10-05 19:13   ` Tom Zander
2015-10-05 19:41     ` Gregory Maxwell
2015-10-05 20:05       ` Steven Pine
2015-10-05 20:21         ` Milly Bitcoin
2015-10-06  7:17           ` cipher anthem
2015-10-06  7:20             ` Eric Lombrozo
2015-10-06  7:29               ` Marcel Jamin
2015-10-06  8:34                 ` NotMike Hearn
2015-10-06 19:40                   ` naama.kates
2015-10-05 20:28         ` Santino Napolitano
2015-10-05 20:35       ` Tom Zander
2015-10-05 20:54         ` Dave Scotese
2015-10-05 20:56         ` Gregory Maxwell
2015-10-05 21:08           ` Tom Zander
2015-10-05 21:16             ` Milly Bitcoin
2015-10-05 21:26             ` Gregory Maxwell
2015-10-06  7:14               ` Tom Zander
2015-10-05 21:27             ` Peter R
2015-10-05 21:30               ` Gregory Maxwell
2015-10-05 21:36                 ` Milly Bitcoin
2015-10-05 21:37                 ` Peter R
2015-10-06  1:37           ` Tom Harding
2015-10-06  3:20             ` Peter R
2015-10-06  3:39               ` Milly Bitcoin
2015-10-06  4:54                 ` Luke Dashjr
2015-10-06  5:08                   ` Milly Bitcoin
2015-10-06  5:49                     ` Milly Bitcoin
2015-10-06  5:53                       ` Luke Dashjr
2015-10-06  6:03                         ` Milly Bitcoin
2015-10-06 22:14                       ` phm [this message]
2015-10-06  5:07               ` NotMike Hearn
2015-10-06  5:33                 ` Peter R
2015-10-05 19:36   ` Milly Bitcoin
2015-10-05 23:18 ` Eric Lombrozo
2015-10-06 17:28 ` Venzen Khaosan
2015-10-07  0:04   ` Sergio Demian Lerner

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=561447B0.3030903@gmail.com \
    --to=moonpunter@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=milly@bitcoins.info \
    /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