From fcca4ab05dea3b199d6d85e03ec47e8464b22e7c Mon Sep 17 00:00:00 2001 From: Harald Hope Date: Fri, 6 Apr 2018 20:49:16 -0700 Subject: [PATCH] readme update. --- README.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.txt b/README.txt index de68d71..fb613d4 100644 --- a/README.txt +++ b/README.txt @@ -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: