To make things easier in the future, always make the change to dev, like all other changes. Then, if a documentation change must be on master before the next release, you can just git cherry-pick commitid to "copy" the change to the master branch
To make things easier in the future, always make the change to dev, like all other changes. Then, if a documentation change *must* be on master before the next release, you can just `git cherry-pick commitid` to "copy" the change to the master branch
- Updated table on top of README
- Changed version specific instructions
- Removed SDX link, as that is not Hush
- Added back the Raspberry Pi ARM CPU info back under "Install on ARM Architecture"
- Changed Supportd and Socials section to use native Markdown instead of HTML
- Changed numbered lists to native Markdown format
README was changed only on master, but we need to merge it into dev to avoid conflicts when merging from dev to master in the future.
To make things easier in the future, always make the change to dev, like all other changes. Then, if a documentation change must be on master before the next release, you can just
git cherry-pick commitidto "copy" the change to the master branchThe Android link points to SDX android and not the Hush Android Wallet.
Earn bountydoes not point to anythingWhy does
What is DragonX?appear in the top table?Changing this README now invalidates this video tutorial: https://videos.hush.is/w/3kKQt81r7UUPWLHVuwK2BZ
"Official Explorers" section appears out of place, as it is before Windows cross compilation section
In "Where can I buy Hush?" section, would it look better to have small clickable images for the exchanges instead of listing the URLs?
e91cbff565into dev 1 month agoe91cbff565.