On Thu, 26 Jun 2014 13:01:05 -0500 Yaakov Selkowitz <yselkowi@xxxxxxxxxx> wrote: > On 2014-06-26 11:17, Richard Hughes wrote: > > On 26 June 2014 17:02, Simone Caronni <negativo17@xxxxxxxxx> wrote: > >> +1 from me! > > > > If it's a trivial patch then I think it makes sense to just do it. > > From someone that touches hundreds of different projects every > > month, I've found it's better to ask forgiveness than permission :) > > As previously stated, that only works if you are a provenpackager. > The question is for those of us who are not, but are trying to help. > > This seems to be particularly needed around mass rebuilds, which IMHO > should be an "all-hands-on-deck" time. For example, I've been going > through the sizable F21FTBFS list[1][2], looking for arm-specific > bugs and fixing what else I can along the way. So far most of my > ~100 patches are just bitrotting in bugzilla, while branching is less > than two weeks away. > > As a newcomer to Fedora development, is there something else I should > doing to get these patches reviewed and committed? I'm pretty swamped, but I'm happy to go through them as time permits and help apply/build them. I assume they are attached to each of the FTBFS bugs? If other provenpackgers have time it would be great to apply these before branching. kevin
Attachment:
signature.asc
Description: PGP signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
