[rhel6-branch] Fix typo from commit ed3caa7b (#1039051)

Chris Lumens clumens at redhat.com
Thu Jun 5 14:30:14 UTC 2014


> Well, I didn't really mean it seriously - I'm afraid static checking is
> not really doable due to the signal-to-noise-ration which we just can't
> change due to the big code changes this would require.

Right, for rhel6-branch.  For rhel7-branch I think we are better
positioned.

> Still, the question might still be valid for the RHEL7 branch - what
> about changes that fix Pylint reported issues but not have any bug
> associated with them ?

If pylint reports an issue that was introduced by some patch that was
added for some bug report, we should be able to commit a fix with
Related: <that bug number>.  If it's general stuff we need to do to get
pylint output empty so we can start using it for real, we should see
about getting a bug opened for it now to use for committing fixes.
We're right at the beginning of RHEL7.  There's no reason we should make
things harder on ourselves in the years to come.

- Chris


More information about the anaconda-patches mailing list