From: Jarod Wilson <jarod@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Josh Boyer <jwboyer@fedoraproject.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <greg@kroah.com>
Subject: Re: Linux-4.X-rcY patches can't be applied with git?
Date: Mon, 24 Oct 2016 19:18:46 -0400 [thread overview]
Message-ID: <20161024231846.GK42084@redhat.com> (raw)
In-Reply-To: <CA+55aFwQvOu=K-3wH06w6yvPm3JHd6hYV7sxs67Y4aK78FiCLA@mail.gmail.com>
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@redhat.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@redhat.com
next prev parent reply other threads:[~2016-10-24 23:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 18:25 Linux-4.X-rcY patches can't be applied with git? Jarod Wilson
2016-10-24 19:24 ` Linus Torvalds
2016-10-24 21:02 ` Josh Boyer
2016-10-24 21:10 ` Linus Torvalds
2016-10-24 21:27 ` Jarod Wilson
2016-10-24 21:45 ` Linus Torvalds
2016-10-24 23:18 ` Jarod Wilson [this message]
2016-10-25 0:06 ` Linus Torvalds
2016-10-25 2:49 ` Jarod Wilson
2016-10-25 11:36 ` Josh Boyer
2016-10-29 21:08 ` Linus Torvalds
2016-10-31 13:15 ` Laura Abbott
2016-10-31 14:55 ` Jarod Wilson
2016-11-08 20:43 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161024231846.GK42084@redhat.com \
--to=jarod@redhat.com \
--cc=greg@kroah.com \
--cc=jwboyer@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).