mirror of
https://github.com/smxi/inxi.git
synced 2024-11-16 16:21:39 +00:00
more edits
This commit is contained in:
parent
31e1a933a0
commit
4e4c0d8e14
|
@ -30,6 +30,16 @@ Fixes:
|
||||||
[hint bsd users, do NOT file issues that you want fixed and then not provide
|
[hint bsd users, do NOT file issues that you want fixed and then not provide
|
||||||
all the data required in a prompt and timely manner, otherwise, really,
|
all the data required in a prompt and timely manner, otherwise, really,
|
||||||
why did you file the issue?].
|
why did you file the issue?].
|
||||||
|
|
||||||
|
Note: the fix basically just rejects any row from lsusb that does not have the
|
||||||
|
expected syntax/value in the expected place, which was I think the right
|
||||||
|
solution given that the change was random, broke expected syntax for lsusb, and
|
||||||
|
wasn't really integrateable into existing inxi usb logic, so why fight it?
|
||||||
|
Given that at least 99.99% of all lsusb output in the world, including by the
|
||||||
|
way OpenBSD's [not sure about most recent version], shows the expected values in
|
||||||
|
the expected place, I could see no value in creating a convoluted work-around
|
||||||
|
for a non core bsd tool in the first place, so that's what I didn't do.
|
||||||
|
|
||||||
See the README.txt for what to do to get issues really handed in BSDs.
|
See the README.txt for what to do to get issues really handed in BSDs.
|
||||||
|
|
||||||
Changes:
|
Changes:
|
||||||
|
|
Loading…
Reference in a new issue