Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933445AbcKQRCP (ORCPT ); Thu, 17 Nov 2016 12:02:15 -0500 Received: from mail-yb0-f196.google.com ([209.85.213.196]:33237 "EHLO mail-yb0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754341AbcKQRCL (ORCPT ); Thu, 17 Nov 2016 12:02:11 -0500 MIME-Version: 1.0 In-Reply-To: References: <20161107075524.49d83697@vento.lan> <11020459.EheIgy38UF@wuerfel> <20161116182633.74559ffd@vento.lan> <2923918.nyphv1Ma7d@wuerfel> From: Linus Torvalds Date: Thu, 17 Nov 2016 08:04:37 -0800 X-Google-Sender-Auth: 1QcBlJjMCS_tn1Z4g5sZlF0nrxQ Message-ID: Subject: Re: [Ksummit-discuss] Including images on Sphinx documents To: Arnd Bergmann Cc: Mauro Carvalho Chehab , ksummit-discuss@lists.linuxfoundation.org, Josh Triplett , "open list:DOCUMENTATION" , Linux Kernel Mailing List , Linux Media Mailing List 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: 559 Lines: 13 On Thu, Nov 17, 2016 at 8:02 AM, Linus Torvalds wrote: > > No. That is how I *noticed* the issue. Those stupid pdf binary files > have been around forever, I just didn't notice until the Fedora people > started complaining about the patches. Side note: my release patches these days enable both "--binary" and "-M", so they require "git apply" now. So we handle the binaries fine in patches now, but as mentioned, that was just what made me notice, it wasn't a fix for the deeper ("source") problem. Linus