linux-kernel - Re: Linux-4.X-rcY patches can't be applied with git?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 24 Oct 2016 19:18:46 -0400
From:   Jarod Wilson <jarod@...hat.com>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Josh Boyer <jwboyer@...oraproject.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Greg Kroah-Hartman <greg@...ah.com>
Subject: Re: Linux-4.X-rcY patches can't be applied with git?

On Mon, Oct 24, 2016 at 02:45:01PM -0700, Linus Torvalds wrote:
> On Mon, Oct 24, 2016 at 2:27 PM, Jarod Wilson <jarod@...hat.com> wrote:
> >
> > Yes and no. What are these non-git people doing with the patches? Since
> > patch won't apply them, are they just reading them for personal
> > enlightenment?
> 
> Oh, patch applies them fine.
> 
> They might end up not seeing some of the updates to binary files,
> that's all. So things like the logo updates or some pdf file might not
> work out for them, but that doesn't mean that they can't use the patch
> and the resulting kernel.

Ah, you're right, of course. I was conflating "patch won't apply them"
with "rpmbuild fails, because patch returns an error code due to the
binary bits failing to apply".

But in that case, what if your patch generation script used a filter to
exclude those binary files? No harm to that target audience, and it would
actually make them behave better for distro builds. Though that might be
counter to the goal of making them disappear entirely. :)

-- 
Jarod Wilson
jarod@...hat.com