Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755620AbcJYAGr (ORCPT ); Mon, 24 Oct 2016 20:06:47 -0400 Received: from mail-oi0-f66.google.com ([209.85.218.66]:35292 "EHLO mail-oi0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753232AbcJYAGo (ORCPT ); Mon, 24 Oct 2016 20:06:44 -0400 MIME-Version: 1.0 In-Reply-To: <20161024231846.GK42084@redhat.com> References: <20161024182503.GH42084@redhat.com> <20161024212754.GI42084@redhat.com> <20161024231846.GK42084@redhat.com> From: Linus Torvalds Date: Mon, 24 Oct 2016 17:06:42 -0700 X-Google-Sender-Auth: uRKED0DQFj1rqrg50p0W6gVVZi0 Message-ID: Subject: Re: Linux-4.X-rcY patches can't be applied with git? To: Jarod Wilson Cc: Josh Boyer , Linux Kernel Mailing List , Greg Kroah-Hartman Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1104 Lines: 26 On Mon, Oct 24, 2016 at 4:18 PM, Jarod Wilson 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