readme update

This commit is contained in:
Harald Hope 2023-09-21 20:12:55 -07:00
parent ffe179aef6
commit a65a6d5e77

View file

@ -2,8 +2,8 @@
README for inxi-perl development branch: pinxi README for inxi-perl development branch: pinxi
================================================================================ ================================================================================
FILE: README.txt FILE: README.txt
VERSION: 1,0 VERSION: 1,1
DATE: 2022-09-18 DATE: 2022-09-21
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
CODEBERG SOURCE REPO CODEBERG SOURCE REPO
@ -19,9 +19,10 @@ pinxi -U to update one time to get the new codeberg updating URLs.
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
Remember that is is NOT the master branch of inxi, this is the master branch of Remember that is is NOT the master branch of inxi, this is the old inxi-perl
pinxi, the development version of inxi, aka, next inxi, and as such, this should branch of pinxi, the development version of inxi, aka, next inxi, and as such,
only be used by expert users. this should only be used by expert users. pinxi how has its own repo at
codeberg.
Please file issue reports or feature requests at: Please file issue reports or feature requests at:
@ -31,9 +32,9 @@ or if you prefer the master inxi repo:
https://codeberg.org/smxi/inxi https://codeberg.org/smxi/inxi
The Codeberg inxi branch inxi-perl will be mirrored to Github until the inxi The github inxi-perl branch will be retained so users can update from it, but
repo refactor is done, after that, no updates to github repos will be made. Some it should not be used for any other purpose, so if you are here, go to codeberg
time after that, the code will be removed. and start over!
Please take the time to read this helpful article from the Software Freedom Please take the time to read this helpful article from the Software Freedom
Conservancy: Conservancy: