diff options
| author | 2018-06-04 23:20:59 -0400 | |
|---|---|---|
| committer | 2018-06-04 23:20:59 -0400 | |
| commit | d04e6727be6cbf207739eb675f0cda4012a1274e (patch) | |
| tree | 7b973830b51f5f9902dc9013013a1c7c123d5fbb /README.txt | |
| parent | 8e2439019187be5e6576b6a400d48aed4731354a (diff) | |
New upstream version 3.0.11-1upstream/3.0.11-1
Diffstat (limited to 'README.txt')
| -rw-r--r-- | README.txt | 13 |
1 files changed, 6 insertions, 7 deletions
@@ -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: |
