Description of problem: i hate really hate such long lines - maybe it's called by some people DOS era - lines ideally should not be longer that 80 chars. # ovirt-engine-hyper-upgrade --help | awk '{ print length($0),$0 }' 75 usage: ovirt-engine-hyper-upgrade [-h] [--backup] [--backup-dir BACKUP_DIR] 67 [--upgrade-to-rhv UPGRADE_TO_RHV] 0 32 Tool to upgrade RHV environments 0 19 optional arguments: 55 -h, --help show this help message and exit 60 --backup Execute engine-backup before upgrade 25 --backup-dir BACKUP_DIR 118 Directory where the engine-backup will save the backup file. If not provided, it will use /tmp 33 --upgrade-to-rhv UPGRADE_TO_RHV 57 Upgrade to specifc version of RHV 0 15 Example of use: 47 ovirt-engine-hyper-upgrade --upgrade-to-rhv=4.1 Example of use: ovirt-engine-hyper-upgrade --upgrade-to-rhv=4.1 Version-Release number of selected component (if applicable): ovirt-engine-hyper-upgrade-1.0.0-3.el7ev.noarch.rpm How reproducible: 100% Steps to Reproduce: 1. --help 2. 3. Actual results: see if it too trendy with length Expected results: oldschoold unix 80 chars length max (if applicable) Additional info:
https://github.com/oVirt/ovirt-engine-hyper-upgrade/pull/10
ok # ovirt-engine-hyper-upgrade --help | awk '{ print length($0),$0 }' 75 usage: ovirt-engine-hyper-upgrade [-h] [--backup] [--backup-dir BACKUP_DIR] 0 32 Tool to upgrade RHV environments 0 19 optional arguments: 55 -h, --help show this help message and exit 60 --backup Execute engine-backup before upgrade 25 --backup-dir BACKUP_DIR 78 Directory where the engine-backup will save the output 57 If not provided, it will use /tmp 0 15 Example of use: 47 ovirt-engine-hyper-upgrade --upgrade-to-rhv=4.1 [root@10-37-138-240 yum.repos.d]# rpm -q ovirt-engine-hyper-upgrade ovirt-engine-hyper-upgrade-1.0.0-4.el7ev.noarch
BZ<2>Jira Resync