Ben Cotton <bcot...@redhat.com> writes: > ===== Phase 2: Package Updates ===== > Once we have the list of packages that need to be updated, we will > proceed with adding BuildRequires: make to all spec files that require > it. This new BuildRequires will be added to the line after the last > BuildRequires in the spec file. The release number for packages will > '''*not*''' be incremented for this change. > > The spec file updates will be automated and changes will be pushed > directly to dist-git once they are ready.
-1. I think you should use pull requests for this, and continue to believe that mass-pushing changes to dist-git is an abuse of provenpackager. Thanks, --Robbie
signature.asc
Description: PGP signature
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
