forked from ROIV/ViorCoin-Wallet
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
70 changed files
with
643 additions
and
821 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,23 +1,20 @@ | ||
Copyright (c) 2014 ViorCoin Developers | ||
Copyright (c) 2014 BlackCoin Developers | ||
Copyright (c) 2013-2014 NovaCoin Developers | ||
Copyright (c) 2011-2012 PPCoin Developers | ||
Copyright (c) 2009-2014 Bitcoin Developers | ||
|
||
Permission is hereby granted, free of charge, to any person obtaining a copy | ||
of this software and associated documentation files (the "Software"), to deal | ||
in the Software without restriction, including without limitation the rights | ||
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | ||
copies of the Software, and to permit persons to whom the Software is | ||
furnished to do so, subject to the following conditions: | ||
|
||
The above copyright notice and this permission notice shall be included in | ||
all copies or substantial portions of the Software. | ||
|
||
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR | ||
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, | ||
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE | ||
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER | ||
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, | ||
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN | ||
THE SOFTWARE. | ||
Copyright (c) 2014 ViorCoin Developers | ||
CCopyright (c) 2009-2014 Bitcoin Developers | ||
|
||
Permission is hereby granted, free of charge, to any person obtaining a copy | ||
of this software and associated documentation files (the "Software"), to deal | ||
in the Software without restriction, including without limitation the rights | ||
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | ||
copies of the Software, and to permit persons to whom the Software is | ||
furnished to do so, subject to the following conditions: | ||
|
||
The above copyright notice and this permission notice shall be included in | ||
all copies or substantial portions of the Software. | ||
|
||
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR | ||
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, | ||
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE | ||
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER | ||
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, | ||
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN | ||
THE SOFTWARE. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,9 +1,9 @@ | ||
Building ViorCoin | ||
|
||
See doc/readme-qt.rst for instructions on building ViorCoin QT, | ||
the intended-for-end-users, nice-graphical-interface, reference | ||
implementation of ViorCoin. | ||
|
||
See doc/build-*.txt for instructions on building ViorCoins, | ||
the intended-for-services, no-graphical-interface, reference | ||
implementation of ViorCoind. | ||
Building ViorCoin | ||
See doc/readme-qt.rst for instructions on building ViorCoin QT, | ||
the intended-for-end-users, nice-graphical-interface, reference | ||
implementation of ViorCoin. | ||
See doc/build-*.txt for instructions on building ViorCoins, | ||
the intended-for-services, no-graphical-interface, reference | ||
implementation of ViorCoind. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,32 +1,32 @@ | ||
|
||
ViorCoin development tree | ||
|
||
ViorCoin is a PoS-based cryptocurrency. | ||
|
||
Development process | ||
=========================== | ||
|
||
Developers work in their own trees, then submit pull requests when | ||
they think their feature or bug fix is ready. | ||
|
||
The patch will be accepted if there is broad consensus that it is a | ||
good thing. Developers should expect to rework and resubmit patches | ||
if they don't match the project's coding conventions (see coding.txt) | ||
or are controversial. | ||
|
||
The master branch is regularly built and tested, but is not guaranteed | ||
to be completely stable. Tags are regularly created to indicate new | ||
stable release versions of ViorCoin. | ||
|
||
Feature branches are created when there are major new features being | ||
worked on by several people. | ||
|
||
From time to time a pull request will become outdated. If this occurs, and | ||
the pull is no longer automatically mergeable; a comment on the pull will | ||
be used to issue a warning of closure. The pull will be closed 15 days | ||
after the warning if action is not taken by the author. Pull requests closed | ||
in this manner will have their corresponding issue labeled 'stagnant'. | ||
|
||
Issues with no commits will be given a similar warning, and closed after | ||
15 days from their last activity. Issues closed in this manner will be | ||
labeled 'stale'. | ||
ViorCoin development tree | ||
ViorCoin is a PoS-based cryptocurrency. | ||
Development process | ||
=========================== | ||
Developers work in their own trees, then submit pull requests when | ||
they think their feature or bug fix is ready. | ||
The patch will be accepted if there is broad consensus that it is a | ||
good thing. Developers should expect to rework and resubmit patches | ||
if they don't match the project's coding conventions (see coding.txt) | ||
or are controversial. | ||
The master branch is regularly built and tested, but is not guaranteed | ||
to be completely stable. Tags are regularly created to indicate new | ||
stable release versions of ViorCoin. | ||
Feature branches are created when there are major new features being | ||
worked on by several people. | ||
From time to time a pull request will become outdated. If this occurs, and | ||
the pull is no longer automatically mergeable; a comment on the pull will | ||
be used to issue a warning of closure. The pull will be closed 15 days | ||
after the warning if action is not taken by the author. Pull requests closed | ||
in this manner will have their corresponding issue labeled 'stagnant'. | ||
Issues with no commits will be given a similar warning, and closed after | ||
15 days from their last activity. Issues closed in this manner will be | ||
labeled 'stale'. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,32 +1,32 @@ | ||
|
||
ViorCoin development tree | ||
|
||
ViorCoin is a PoS-based cryptocurrency. | ||
|
||
Development process | ||
=========================== | ||
|
||
Developers work in their own trees, then submit pull requests when | ||
they think their feature or bug fix is ready. | ||
|
||
The patch will be accepted if there is broad consensus that it is a | ||
good thing. Developers should expect to rework and resubmit patches | ||
if they don't match the project's coding conventions (see coding.txt) | ||
or are controversial. | ||
|
||
The master branch is regularly built and tested, but is not guaranteed | ||
to be completely stable. Tags are regularly created to indicate new | ||
stable release versions of ViorCoin. | ||
|
||
Feature branches are created when there are major new features being | ||
worked on by several people. | ||
|
||
From time to time a pull request will become outdated. If this occurs, and | ||
the pull is no longer automatically mergeable; a comment on the pull will | ||
be used to issue a warning of closure. The pull will be closed 15 days | ||
after the warning if action is not taken by the author. Pull requests closed | ||
in this manner will have their corresponding issue labeled 'stagnant'. | ||
|
||
Issues with no commits will be given a similar warning, and closed after | ||
15 days from their last activity. Issues closed in this manner will be | ||
labeled 'stale'. | ||
|
||
ViorCoin development tree | ||
|
||
ViorCoin is a PoS-based cryptocurrency. | ||
|
||
Development process | ||
=========================== | ||
|
||
Developers work in their own trees, then submit pull requests when | ||
they think their feature or bug fix is ready. | ||
|
||
The patch will be accepted if there is broad consensus that it is a | ||
good thing. Developers should expect to rework and resubmit patches | ||
if they don't match the project's coding conventions (see coding.txt) | ||
or are controversial. | ||
|
||
The master branch is regularly built and tested, but is not guaranteed | ||
to be completely stable. Tags are regularly created to indicate new | ||
stable release versions of ViorCoin. | ||
|
||
Feature branches are created when there are major new features being | ||
worked on by several people. | ||
|
||
From time to time a pull request will become outdated. If this occurs, and | ||
the pull is no longer automatically mergeable; a comment on the pull will | ||
be used to issue a warning of closure. The pull will be closed 15 days | ||
after the warning if action is not taken by the author. Pull requests closed | ||
in this manner will have their corresponding issue labeled 'stagnant'. | ||
|
||
Issues with no commits will be given a similar warning, and closed after | ||
15 days from their last activity. Issues closed in this manner will be | ||
labeled 'stale'. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.