Monzero core node, command-line wallet, consensus code, and release tooling. https://code.monzero.org/monzero-core.git/atom?h=v0.10.2 2017-02-22T07:55:06Z 2017-02-22T07:55:06Z Riccardo Spagni ric@spagni.net 2017-02-22T07:55:06Z urn:sha1:27b477f68d4174750d6bfb3ec1ca3c7d6efb1fd8 2017-02-21T10:25:58Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-02-21T10:25:58Z urn:sha1:13cd544de3aedc48000b4a0692b04464244334aa 2017-02-20T22:58:16Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-02-18T16:30:29Z urn:sha1:f640512c53caca9d7c3c69802841d174818cf953 It just checks and prints a message if there is a new version for now. 2017-01-16T08:49:28Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-01-16T08:49:07Z urn:sha1:e389bd9e60dccc720cc65497b6330d81ca16c465 2017-01-16T00:25:46Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-01-01T16:34:23Z urn:sha1:5833d66f6540e7b34e10ddef37c2b67bd501994b This replaces the epee and data_loggers logging systems with a single one, and also adds filename:line and explicit severity levels. Categories may be defined, and logging severity set by category (or set of categories). epee style 0-4 log level maps to a sensible severity configuration. Log files now also rotate when reaching 100 MB. To select which logs to output, use the MONERO_LOGS environment variable, with a comma separated list of categories (globs are supported), with their requested severity level after a colon. If a log matches more than one such setting, the last one in the configuration string applies. A few examples: This one is (mostly) silent, only outputting fatal errors: MONERO_LOGS=*:FATAL This one is very verbose: MONERO_LOGS=*:TRACE This one is totally silent (logwise): MONERO_LOGS="" This one outputs all errors and warnings, except for the "verify" category, which prints just fatal errors (the verify category is used for logs about incoming transactions and blocks, and it is expected that some/many will fail to verify, hence we don't want the spam): MONERO_LOGS=*:WARNING,verify:FATAL Log levels are, in decreasing order of priority: FATAL, ERROR, WARNING, INFO, DEBUG, TRACE Subcategories may be added using prefixes and globs. This example will output net.p2p logs at the TRACE level, but all other net* logs only at INFO: MONERO_LOGS=*:ERROR,net*:INFO,net.p2p:TRACE Logs which are intended for the user (which Monero was using a lot through epee, but really isn't a nice way to go things) should use the "global" category. There are a few helper macros for using this category, eg: MGINFO("this shows up by default") or MGINFO_RED("this is red"), to try to keep a similar look and feel for now. Existing epee log macros still exist, and map to the new log levels, but since they're used as a "user facing" UI element as much as a logging system, they often don't map well to log severities (ie, a log level 0 log may be an error, or may be something we want the user to see, such as an important info). In those cases, I tried to use the new macros. In other cases, I left the existing macros in. When modifying logs, it is probably best to switch to the new macros with explicit levels. The --log-level options and set_log commands now also accept category settings, in addition to the epee style log levels. 2017-01-05T01:11:05Z MoroccanMalinois MoroccanMalinois@protonmail.com 2017-01-05T01:11:05Z urn:sha1:80abc3bc4a73f3ba6ffd40b1a03de0cc4d01e3c9 2016-10-27T22:22:07Z NanoAkron nanoakron@users.noreply.github.com 2016-10-27T22:17:02Z urn:sha1:54c9400fbe6c4aa8bab5b8124c9cb8a2642f810f 2016-09-01T14:47:43Z redfish redfish@galactica.pw 2016-08-29T18:23:57Z urn:sha1:e374ae7eebedebced6147f78d4027f510f77e25a 2016-08-29T23:57:55Z NanoAkron nanoakron@users.noreply.github.com 2016-08-29T10:13:55Z urn:sha1:cf10e05cc6a0ed495dbdd44ec3a76b964b14edba Adds 64-bit ARMv8 handling to CMakeLists.txt and implements GCC flags for two errata on the Cortex-A53 present on every chip in revision 0: https://developer.arm.com/docs/epm048406/latest/arm-processor-cortex-a53-mpcore-product-revision-r0-software-developers-errata-notice 835769 affects 64-bit multiply accumulate 843419 affects internal page addressing Rewritten to build on @radfish's changes Updated to address @radfish's points 2016-08-28T20:49:09Z Riccardo Spagni ric@spagni.net 2016-08-28T20:49:09Z urn:sha1:53a0997a260472d4efb777e8aaa90230cd229421 1c7d3b0 cmake: define ARM var for all ARM arch variants (redfish) 6fe543d cmake: ARM: exclude libunwind in static build (redfish) 397b720 make: remove NO_AES from arm targets (redfish) 57ca3f3 make: make the ARM release targets statically linked (redfish) 43c07a1 readme: editted install/build instructions for clarity (redfish) a0d4058 Revert "makefile: remove unnecessary ARM-specific targets" (redfish) c2bc34b Revert "Interpret x86_64 as x86-64 for architecture" (redfish) c54b9a1 cmake: don't set ARCH from CMAKE_SYSTEM_PROCESSOR (redfish)