dmitriy.kazimirov/inxi
1
0
Fork 0
mirror of https://github.com/smxi/inxi.git synced 2024-11-16 16:21:39 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

readme edits

Browse source
This commit is contained in:
Harald Hope 2018-04-11 15:29:45 -07:00
parent 1b189a9362
commit 7103f8ecb1
1 changed files with 6 additions and 11 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
README.txt
View file

@ -19,18 +19,13 @@ OR easy to remember shortcut (which redirects to github):
wget -Nc https://smxi.org/inxi wget -Nc https://smxi.org/inxi
wget -Nc smxi.org/inxi wget -Nc smxi.org/inxi
NOTE: I have deleted the master-plain branch to avoid confusion Every current master branch commit is the active release, all past
since I've removed the legacy .gz files from the branch, which were commits are not supported. Tagging is purely a formality that certain
the only reasons for its existence. 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.
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.
Every current commit is the active release, all past commits are not
supported. Tagging is purely a formality that certain distros can't
figure out how to do without, that's all.
NOTE: JUST BECAUSE GITHUB CALLS MY TAGGED COMMITS 'RELEASES' DOES
NOT MEAN THEY ARE RELEASES!!! I can't change the words on the tag page.
They are tagged commmits, period. I did not want to use tags precisely They are tagged commmits, period. I did not want to use tags precisely
to avoid the idea that inxi has any release that exists that is other to avoid the idea that inxi has any release that exists that is other
than it's current master version, but I decided that it was less pain than it's current master version, but I decided that it was less pain