dmnks left a comment (rpm-software-management/rpm#3639)
> This is an exceedingly rare thing to do.
Not quite as rare:
```
git add [--verbose | -v] [--dry-run | -n] [--force | -f] [--interactive | -i]
[--patch | -p]
[--edit | -e] [--[no-]all | -A | --[no-]ignore-removal | [--update
| -u]] [--sparse]
[--intent-to-add | -N] [--refresh] [--ignore-errors]
[--ignore-missing] [--renormalize]
[--chmod=(+|-)x] [--pathspec-from-file=<file> [--pathspec-file-nul]]
[--] [<pathspec>...]
```
That said, as you can see, this is nearly impossible to visually parse and/or
make any sense of it.
So, I agree, the rule of thumb should be something like:
1) Only list major modes of operation, on per line (much like what we already
do in `rpm(1)`)
2) Only include the most useful options in given mode, not all of them
This is really a case-by-case thing, though, so no point in making up some
strict rules, I guess...
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/3639#issuecomment-2704333223
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/pull/3639/[email protected]>_______________________________________________
Rpm-maint mailing list
[email protected]
https://lists.rpm.org/mailman/listinfo/rpm-maint
