-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 12/08/14 09:54 AM, Ian Stakenvicius wrote: > > Perhaps we need to have a less-important repoman warning level > (something that can be quieted with a flag) for things like this? > In terms of DESCRIPTION consistency I don't see it being a bad > thing that we have the warning, but i also don't see a point in > changing the entire tree to get rid of 3000 bytes, esp. since the > ChangeLog entries added to the tree will add at least 30,000 bytes > :) >
I'm wondering what everyone thinks of having a --nonag option to repoman and shoving some of the more trivial/style-related repoman 'warnings' into a 'nag' level warning? IIRC at least one of the QA team members is so tired of the warnings that they want to make every single one of them errors; the --nonag option would allow those warnings to remain in repoman (ie to help guide new dev's or non-dev's using repoman on their local repos) but since they don't relate to actual technical breakage they can just be turned off during QA runs, etc. Thoughts? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlPqHwoACgkQ2ugaI38ACPAVvgEAqNY3pl+QartxGxiTnEPuycl3 4za+QK26KuNUGO0RJewA/0EIV6z92TG3hr+eLDViIJxfdB0GVTl6JV6ha/EQUZcY =49jq -----END PGP SIGNATURE-----
