History log of /libevent-2.1.12/LICENSE (Results 1 – 7 of 7)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
Revision tags: release-2.2.1-alpha, release-2.1.12-stable, release-2.1.11-stable, release-2.1.10-stable, release-2.1.9-beta, release-2.0.23-beta, release-2.1.8-stable, release-2.1.7-rc, release-2.1.6-beta, release-2.0.22-stable, release-1.4.15-stable, release-2.1.5-beta, release-2.1.4-alpha, release-2.1.3-alpha, release-2.1.2-alpha, release-2.0.21-stable, release-2.0.20-stable, release-2.0.19-stable
# 2c470452 23-Apr-2012 Nick Mathewson <[email protected]>

Implement fast/precise monotonic clocks on Windows

This uses code from libutp, which was released under the MIT
license; see evutil_time.c and LICENSE changes.


Revision tags: release-2.1.1-alpha, release-2.0.18-stable, release-2.0.17-stable
# e49e2891 10-Feb-2012 Nick Mathewson <[email protected]>

Update copyright notices to 2012


Revision tags: release-2.0.16-stable
# 3c824bd3 24-Oct-2011 Nick Mathewson <[email protected]>

Update copyright dates to 2011.


Revision tags: release-2.0.15-stable, release-2.0.14-stable, release-2.0.13-stable, release-2.0.12-stable, release-2.0.11-stable, release-2.0.10-stable, release-2.0.9-rc, release-2.0.8-rc, release-2.0.7-rc, release-2.0.6-rc, release-1.4.14b-stable, release-1.4.14-stable, release-2.0.5-beta
# 38b7b571 04-Mar-2010 Nick Mathewson <[email protected]>

Add Christopher Clark and Maxim Yegorushkin to the LICENSE file


# 17efc1cd 04-Mar-2010 Nick Mathewson <[email protected]>

Update all our copyright notices to say "2010"


Revision tags: release-2.0.4-alpha
# e15e1e94 18-Feb-2010 Nick Mathewson <[email protected]>

Add the arc4random.c license to the LICENSE file.


# 70670067 19-Jan-2010 Nick Mathewson <[email protected]>

Add a LICENSE file so people can find our license easily

For what it's worth, we are aware that "Copyright $YEAR $NAME" is
sufficient notice of copyright on software under US law and
Internationally

Add a LICENSE file so people can find our license easily

For what it's worth, we are aware that "Copyright $YEAR $NAME" is
sufficient notice of copyright on software under US law and
Internationally, and saying Copyright (c) $YEAR $NAME is a bit nutty.
The character sequence (c) has never been ruled to have the same force
in US law as the actual copyright symbol, and that neither of these
US-specific symbols adds anything of value beyond saying "Copyright"
since the Berne convention took effect in the US back in 1989.

Similarly, saying "all rights reserved" doesn't do anything magical
unless your software goes in a time-warp back to when the Buenos Aires
Convention was the general rule. (And what will they run it on back
then?) And what would even lead you to say "All Rights Reserved" when
you're explicitly granting most of those rights to anybody receiving
the work in accordance with the 3-clause BSD license?

But still the FOSS community retains these ritual notations out of a
kind of cargo-cult lawyering. Who knows? Perhaps one day, if we
write our copyright notices ineptly enough, John Frum will come and
give us a DFSG-compatible license that everybody can get behind.

(Also, I am not a lawyer. The above should not be taken as legal
advice. -- Nick)

show more ...