Update Home

smxi 2023-09-18 01:08:26 +00:00
parent afa3a4bbdf
commit 9e873e1c38

@ -13,7 +13,7 @@ The following are the resources available for inxi support, help, documentation,
* [inxi core mission](https://smxi.org/docs/inxi-core-mission.htm) - useful for potential contributors who might not understand why things in inxi are done the way they are. Covers support for Legacy OS/Hardware, optimizations, and primary philosophy. * [inxi core mission](https://smxi.org/docs/inxi-core-mission.htm) - useful for potential contributors who might not understand why things in inxi are done the way they are. Covers support for Legacy OS/Hardware, optimizations, and primary philosophy.
* [inxi json/xml output](https://smxi.org/docs/inxi-json-xml-output.htm) - understanding the json/xml data structures so you can process it. DO NOT ASK ME FOR PROGRAMMING HELP! * [inxi json/xml output](https://smxi.org/docs/inxi-json-xml-output.htm) - understanding the json/xml data structures so you can process it. DO NOT ASK ME FOR PROGRAMMING HELP!
* [inxi support forums](http://techpatterns.com/forums/forum-33.html) - post actual discussion type issues here, or use the issues tracker here, makes no difference, except the forum will be way more sticky and visible over time. * [inxi support forums](http://techpatterns.com/forums/forum-33.html) - post actual discussion type issues here, or use the issues tracker here, makes no difference, except the forum will be way more sticky and visible over time.
* [inxi issue tracker](https://github.com/smxi/inxi/issues) - use the github issue tracker/bug reporter to report issues/bugs. * [inxi issue tracker](https://codeberg.org/smxi/inxi/issues) - use the codeberg.org issue tracker/bug reporter to report issues/bugs.
* inxi IRC support: channel #smxi on irc.oftc.net or irc.libera.chat - sometimes IRC support is faster or more efficient. * inxi IRC support: channel #smxi on irc.oftc.net or irc.libera.chat - sometimes IRC support is faster or more efficient.
* For git, the following branches are of interest (note: all pinxi/inxi branches support the -U self-updater command for easy updating once you have installed that branch. one and two would overwrite inxi master version, which is why they are almost never used): * For git, the following branches are of interest (note: all pinxi/inxi branches support the -U self-updater command for easy updating once you have installed that branch. one and two would overwrite inxi master version, which is why they are almost never used):
* master - the master main branch. No other version of inxi than the current one in master is supported, so please upgrade your inxi to current before posting any issue or bug reports. See the installation instructions for how to do that. Devs: use inxi-perl pinxi since that is always either ahead or even with master. * master - the master main branch. No other version of inxi than the current one in master is supported, so please upgrade your inxi to current before posting any issue or bug reports. See the installation instructions for how to do that. Devs: use inxi-perl pinxi since that is always either ahead or even with master.