From 2bf67050272cfbdddce02b83f2967d0c5d772de3 Mon Sep 17 00:00:00 2001 From: smxi Date: Thu, 30 Nov 2023 22:14:41 +0000 Subject: [PATCH] Update Home --- Home.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/Home.md b/Home.md index 6b327c9..939fca9 100644 --- a/Home.md +++ b/Home.md @@ -15,13 +15,13 @@ The following are the resources available for inxi support, help, documentation, * [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://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. -* 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. - * inxi-perl - this is the primary development branch, and uses pinxi to let you run inxi and pinxi on same system. - * one - alternate rarely used development branch for inxi. - * two - alternate, even more rarely used development branch for inxi. - * docs - this is the collection of html/css files that you'll find the [inxi documentation](http://smxi.org/docs/inxi.htm) in at [smxi.org](http://smxi.org/). - * tarballs - a weak effort on my part to create a history of inxi. It's a collection of tarballs going back pretty much to the start of inxi, but they are randomly updated, and are NOT a reference point for packagers. They are a reference point for me and for anyone interested in how inxi grew and developed, nothing more. +* For git, the following branches and repos are of interest (note: pinxi and inxi support the -U self-updater command for easy updating once installed. one and two would overwrite inxi master version, which is why they are almost never used): + * master - [codeberg.org/smxi/inxi master](codeberg.org/smxi/inxi/) 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 pinxi since that is always either ahead or even with master. + * one - [codeberg.org/smxi/inxi one](https://codeberg.org/smxi/inxi/src/branch/one) Alternate rarely used development branch for inxi. + * two - [codeberg.org/smxi/inxi two](https://codeberg.org/smxi/inxi/src/branch/two) Alternate rarely used development branch for inxi. + * pinxi - [codeberg.org/smxi/pinxi master](codeberg.org/smxi/pinxi/) (Obsolete: inxi/inxi-perl branch) This is the primary development release. Using pinxi lets you run inxi and pinxi on same system. + * inxi-docs - [codeberg.org/smxi/inxi-docs master](codeberg.org/smxi/inxi-docs/) (Obsolete: inxi/docs branch) This is the collection of html/css files that you'll find the [inxi documentation](http://smxi.org/docs/inxi.htm) in at [smxi.org](http://smxi.org/). + * tarballs - [codeberg.org/smxi/inxi-tarballs master](codeberg.org/smxi/inxi-tarballs/) (Obsolete: inxi/tarballs branch) A weak effort on my part to create a history of inxi. It's a collection of tarballs going back pretty much to the start of inxi, but they are randomly updated, and are NOT a reference point for packagers. They are a reference point for me and for anyone interested in how inxi grew and developed, nothing more. If you have edits or changes for the smxi.org inxi documentation, you can file an issue here. The pages are in git here for your convenience, but please do not put those live anywhere else or google gets confused about which are the real versions. And please don't turn them into wiki pages elsewhere, people tend to do that once, then it gets stagnant and stale, but google doesn't know which is the real version, so please stick to the real documentation always.