From d04e6727be6cbf207739eb675f0cda4012a1274e Mon Sep 17 00:00:00 2001 From: Unit 193 Date: Mon, 4 Jun 2018 23:20:59 -0400 Subject: New upstream version 3.0.11-1 --- README.txt | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) (limited to 'README.txt') diff --git a/README.txt b/README.txt index 1970c17..df66930 100644 --- a/README.txt +++ b/README.txt @@ -66,13 +66,9 @@ OR easy to remember shortcut (which redirects to github): wget -Nc https://smxi.org/inxi wget -Nc smxi.org/inxi -'Tagging' is purely a formality that certain distros can't figure out how to -do without, that's all. A tag is a pointer to a commit, and has no further -meaning. - NOTE: Just because github calls tagged commits 'Releases' does not mean they are releases! I can't change the words on the tag page. They are tagged -commmits, period. +commmits, period. A tag is a pointer to a commit, and has no further meaning. ------------------------------------------------------------------------------- DEVELOPMENT BRANCH: @@ -87,8 +83,11 @@ OR easy to remember shortcut (which redirects to github): wget -Nc https://smxi.org/pinxi wget -Nc smxi.org/pinxi -Once new features have been debugged, tested, and are stable, they will move -to the master branch. +Once new features have been debugged, tested, and are reasonably stable, pinxi +is copied to inxi in the master branch. + +It's a good idea to check with pinxi if you want to make sure your issue has +not been corrected, since pinxi is always equal to or ahead of inxi. ------------------------------------------------------------------------------- LEGACY BRANCH: -- cgit v1.2.3