On Mon, Aug 11, 2014 at 7:15 PM, Chris Murphy <li...@colorremedies.com> wrote: > > On Aug 11, 2014, at 3:28 PM, Chris Murphy <li...@colorremedies.com> wrote: > >> Since it came up at Flock: if it's possible to incorporate this recent >> experiencing testing Btrfs patches it'd be nice. >> >> Two patches listed here, one is based on Btrfs integration branch, the other >> based on 3.16.0. I didn't realize the original patch was based on >> integration branch, which is apparently why it kept failing to apply with >> rpmbuild (and hence patch) on kernel-3.16.0-1.fc21.src.rpm. I'm told in this >> email that git am would have sorted this out for me. (?) >> >> http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg36299.html >> >> Request 1: if there's a more tolerant patch applying method with git that >> could be incorporated, even if it's just a step that converts the patch so >> that rpmbuild/patch will eat it, that would be nice. But if it requires a >> local git clone of upstream's dev branch, then ignore this part because I'm >> not going to do that. I'd sooner ask for a patch that applies onto something >> I'm actually going to build. >> >> Request 2: patches to just get picked up by dropping them somewhere, like >> rpmbuild/SOURCES/*.patch always get picked up and applied, rather than >> requiring two manually entered entries in kernel.spec per patch. > > Request 3: Current instructions call for use of yum, yumdownloader, and > yum-builddep. Can it be done entirely with dnf? I'm not sure what the dnf > equivalent is for yumdownloader or yum-builddep.
I have no idea. None of us use dnf. If someone would like to experiment with what it would take to do this with dnf, that would be a great way for the community to help out. Post the directions to the kernel list and we'll see how they look. josh -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
