Move license to its own LICENSE file.

Mon, 20 Apr 2020 09:31:30 -0500

author
Tuomo Valkonen <tuomov@iki.fi>
date
Mon, 20 Apr 2020 09:31:30 -0500
changeset 123
385d4eada9ed
parent 122
8d2881338a4a
child 126
cf4e7b6f5f5e

Move license to its own LICENSE file.

README.md file | annotate | diff | comparison | revisions
--- a/README.md	Wed Dec 05 08:27:35 2018 -0500
+++ b/README.md	Mon Apr 20 09:31:30 2020 -0500
@@ -91,26 +91,3 @@
 
     security add-generic-password -a myrepo -s borg-backup -w [PASSWORD]
 
-
-## License
-
-This software is distributed under an ANTI-ABUSE LICENSE (aka. *f..k
-copyright and f..k distributions license*), and without any warranty
-whatsoever. If you redistribute this software as part of a larger
-collection/distribution/suite of software, you must do either of the
-following:
-
-(a) Always redistribute the **unmodified** and **latest** version provided
-by the lead author. If the lead author releases a new version (on a specific
-branch, such as 'stable' or 'development'), you must promptly make that new
-version the default version offered to your users (on that specific branch).
-
-(b) Rename the software, and make it obvious that your modified or obsolete
-software is in no way connected to the lead author of the original software.
-The users of your version should under no circumstances be under the
-illusion hat they can contact the lead author or any of the authors of the
-original software if they have any complaints or queries.
-
-Otherwise, do whatever you want with this software. In particular, you may
-freely use code snippets in other projects.
-

mercurial