aboutsummaryrefslogtreecommitdiffstats
path: root/README.txt
diff options
context:
space:
mode:
authorLibravatarUnit 193 <unit193@ubuntu.com>2018-06-23 18:03:20 -0400
committerLibravatarUnit 193 <unit193@ubuntu.com>2018-06-23 18:03:20 -0400
commit6da87c33f67292184b72ce90d0c0e20259d40652 (patch)
tree51200d3917dae4c7ed09c1edd2cb41627f63e03d /README.txt
parent8755496ae0d1653da17759bddef28f56f3c2b5b3 (diff)
parentb2b760d016b72138575770e2a845c7280ceca33d (diff)
Update upstream source from tag 'upstream/3.0.13-1'
Update to upstream version '3.0.13-1' with Debian dir c24f9203a37bbb0c9be408b6571b952d140b6515
Diffstat (limited to 'README.txt')
-rw-r--r--README.txt22
1 files changed, 11 insertions, 11 deletions
diff --git a/README.txt b/README.txt
index df66930..35ce2e2 100644
--- a/README.txt
+++ b/README.txt
@@ -36,7 +36,7 @@ ARM and BSD datasets are particularly appreciated because we simply do not
have enough of those.
===============================================================================
-Make inxi better! Get more support, fix broken items!
+Make inxi better! Expand supported hardware and OS data, fix broken items!
inxi strives to support the widest range of operating systems and hardware,
from the most simple consumer desktops, to the most advanced professional
@@ -291,7 +291,16 @@ for anything other than current master branch. No merges, attempts to patch old
code from old versions, will be considered or accepted. If you are not updated
to the latest inxi, do not file a bug report since it's probably been fixed
ages ago. If your distro isn't packaging a current inxi, then file a bug report
-with them, not here.
+with your packager, not here.
+
+Sys Admin type inxi users always get the first level of support. ie, convince
+us you run real systems and networks, and your issue shoots to the top of the
+line. As do any real bugs. Failure to supply requested debugger data will lead
+to a distinct lack of interest on our part to help you with a bug. ie, saying,
+oh, it doesn't work, doesn't cut it, unless it's obvious why.
+
+inxi is 'rolling release' software, just like Debian Sid, Gentoo, or Arch Linux
+are rolling release GNU/Linux distributions, with no 'release points'.
Distributions should never feel any advantage comes from using old inxi
versions because inxi has as a core promise to you, the end user, that it will
@@ -302,9 +311,6 @@ project violate that core inxi requirement. Old inxi is NOT more stable than
current inxi, it's just old, and lacking in bug fixes and features. For pre 2.9
versions, it's also significantly slower, and with fewer features.
-inxi is 'rolling release' software, just like Debian Sid, Gentoo, or Arch Linux
-are rolling release GNU/Linux distributions, with no 'release points'.
-
Your distro not updating inxi ever, then failing to show something that is
fixed in current inxi is not a bug, and please do not post it here. File the
issue with your distro, not here. Updating inxi in a package pool will NEVER
@@ -314,12 +320,6 @@ update inxi in a package pool of any distro in the world (with one single known
exception, the Slackware based Puppy Linux release, which ships without the
full Perl language. The Debian based one works fine).
-Sys Admin type inxi users always get the first level of support. ie, convince
-us you run real systems and networks, and your issue shoots to the top of the
-line. As do any real bugs. Failure to supply requested debugger data will lead
-to a distinct lack of interest on our part to help you with a bug. ie, saying,
-oh, it doesn't work, doesn't cut it, unless it's obvious why.
-
===============================================================================
INXI VERSION NUMBERING: