summaryrefslogtreecommitdiff
path: root/sys/dev/microcode/tools/array2bin.c
diff options
context:
space:
mode:
authorkre <kre@NetBSD.org>2022-02-02 01:21:34 +0000
committerkre <kre@NetBSD.org>2022-02-02 01:21:34 +0000
commit1d9f2438e6eefa91a376141c24e984ae65a64140 (patch)
treef0c0c5cb5b0229fc73ba154cfd494f172002ad8f /sys/dev/microcode/tools/array2bin.c
parent391c28010df763ba520917c9062459acef66f8b6 (diff)
After (a few days short of) 21 years, revert 1.25, which did nothing except
make the -e option to "fc" fail to work (the commit message was about some other changes entirely, so I an only assume this was committed by mistake). It says a lot about the use of the fc command that no-one noticed that this did not work properly for all this time. Internally in sh, it is possible for built in commands to use either getopt(3) (from libc) or the much simpler internal shell nextopt() routine for option (flag) parsing. However it makes no sense to use getopt() and then access a global variable set only by nextopt() instead of the one getopt() sets (which is what the code had used previously, forever). Use the correct variable again. XXX pullup -9 -8 (-7 -6 -5 ...)
Diffstat (limited to 'sys/dev/microcode/tools/array2bin.c')
0 files changed, 0 insertions, 0 deletions