Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933618AbcKHUnx (ORCPT ); Tue, 8 Nov 2016 15:43:53 -0500 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:58196 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933409AbcKHUnl (ORCPT ); Tue, 8 Nov 2016 15:43:41 -0500 Date: Tue, 8 Nov 2016 21:43:37 +0100 From: Pavel Machek To: Linus Torvalds Cc: Jarod Wilson , Josh Boyer , Linux Kernel Mailing List , Greg Kroah-Hartman Subject: Re: Linux-4.X-rcY patches can't be applied with git? Message-ID: <20161108204337.GB21477@amd> References: <20161024182503.GH42084@redhat.com> <20161024212754.GI42084@redhat.com> <20161024231846.GK42084@redhat.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="QTprm0S8XgL7H0Dt" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2105 Lines: 63 --QTprm0S8XgL7H0Dt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! > > 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 wou= ld > > actually make them behave better for distro builds. Though that might be > > counter to the goal of making them disappear entirely. :) >=20 > 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... >=20 > To be honest, I really would like to not do the tar-balls and patches at = all. >=20 > 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". >=20 > Then I could just enable "--binary" and "-M", and see what happens. >=20 > I suspect that these days, git is so ubiquitous that it's ok. >=20 > And then in a few years, maybe I can just stop doing patches entirely, > having proved the point that everybody already has git ;) Well, having git is not quite the same thing as "having big enough machine to run git on tree as big as kernel". Handheld zaurus was powerful enough to compile kernel (in few hours) but git was pretty painful to use there. I'm now cross-compiling for n900, so problem is gone there, but there is difference between downloading single release, and downloading full history when you are on a slow line... Best regards, Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --QTprm0S8XgL7H0Dt Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlgiOPkACgkQMOfwapXb+vIZHACePPoSDXEhNVGt0aE5rW8aVlHB MvsAn3MbW0ZKQ1JhVTaAcRiC/IRkDGFu =Mh1I -----END PGP SIGNATURE----- --QTprm0S8XgL7H0Dt--