Hi David, I understand that btrfs-progs introduced restrict parameter/option order to distinguish global and sub-command parameter/option.
However it's really annoying if one just want to append some new options to previous command: E.g. # btrfs check /dev/data/btrfs # !! --check-data-csum The last command will fail as current btrfs-progs doesn't allow any option after parameter. Despite the requirement to distinguish global and subcommand option/parameter, is there any other requirement for such restrict option-first-parameter-last policy? If I could implement a enhanced getopt to allow more loose order inside subcomand while still can distinguish global option, will it be accepted (if it's quality is acceptable) ? Thanks, Qu
signature.asc
Description: OpenPGP digital signature
