readme update, clarifications on tagging.

This commit is contained in:
Harald Hope 2018-03-22 18:29:39 -07:00
parent fcf8cbbe27
commit 74cd539e94

View file

@ -15,15 +15,25 @@ NOTE: I have deleted the master-plain branch to avoid confusion
since I've removed the legacy .gz files from the branch, which were
only reasons for its existence.
Every commit is auto-tagged. There ar 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.
I auto tag commits I that I feel are somewhat complete at that stage
of the coding. There ar 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.
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.
NOTE: JUST BECAUSE GITHUB CALLS MY TAGGED COMMITS 'RELEASES' DOES
NOT REPEAT NOT MEAN THEY ARE RELEASES!!! Got it? I can't change the
words 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.
=====================================================================
DEVELOPMENT BRANCH:
All active development is now done on the inxi-perl branch: