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 17:06:42 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Jarod Wilson <jarod@...hat.com>
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 4:18 PM, Jarod Wilson <jarod@...hat.com> wrote:
>
> 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. :)

Heh, I'd rather people get the warning that "oops, something is
incomplete". They can still work with the end result, but at least
they got some indication that hey, that patch didn't work wonderfully
well...

To be honest, I really would like to not do the tar-balls and patches at all.

But maybe rather than saying "it's only for legacy 'patch' users", I
could just say that it's getting phased out, and say "you have to use
'git apply' to apply them".

Then I could just enable "--binary" and "-M", and see what happens.

I suspect that these days, git is so ubiquitous that it's ok.

And then in a few years, maybe I can just stop doing patches entirely,
having proved the point that everybody already has git ;)

                   Linus