dmitriy.kazimirov/inxi
1
0
Fork 0
mirror of https://github.com/smxi/inxi.git synced 2025-01-19 00:47:47 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

readme update.

Browse source
This commit is contained in:
Harald Hope 2018-04-06 20:49:16 -07:00
parent e43933452f
commit fcca4ab05d
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
README.txt
View file

@ -27,11 +27,11 @@ of the coding. There are NO releases, don't even dream of pretending
a tagged release holds any significance at all. I only added auto
tagging to get the maintainers to stop annoying me about tagging.
There is NO repeat NO meaning to the fact a commit is tagged. A tag
is a pointer to a commit, and has no further meaning.
is a pointer to a commit, and has no further meaning.
Every current commit is the active release, all past commits are not
supported. Tagging has ZERO meaning, it's purely a formality that
certain distros can't figure out how to do without, that's all.
certain distros can't figure out how to do without, that's all.
NOTE: JUST BECAUSE GITHUB CALLS MY TAGGED COMMITS 'RELEASES' DOES
NOT REPEAT NOT MEAN THEY ARE RELEASES!!! I can't change the words
@ -39,7 +39,7 @@ on the tag page. 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 than it's current master version, but I
decided that it was less pain to add tags than to argue this point
any further.
any further.
=====================================================================
DEVELOPMENT BRANCH: