mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Linus Torvalds via RT" <kernel-helpdesk@rt.linuxfoundation.org>
To: rdunlap@infradead.org
Cc: linux-kernel@vger.kernel.org
Subject: [Kernel.org Helpdesk #46182] [linuxfoundation.org #46182] Re: Linux 4.14-rc2 (bad patch file on kernel.org)
Date: Sun, 24 Sep 2017 23:43:52 -0400	[thread overview]
Message-ID: <rt-4.4.0-6214-1506311032-730.46182-6-0@linuxfoundation> (raw)
In-Reply-To: <CA+55aFzA365mGSqB7eS=xG82RfJBNy7owF6iTfO7WSmzts-j=g@mail.gmail.com>

On Sun, Sep 24, 2017 at 8:41 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> But I just tried it myself, and get the same breakage. In fact, the
> patch it downloads is exactly 50397184 bytes in size.

Side note: instead of downloading a 50MB patch, you could probably use
the same amount of bandwidth to download and build git, and then use
that to download much smaller incremental updates.

I'm surprised that people still even use those nasty patches and tar-balls.

               Linus

  reply	other threads:[~2017-09-25  3:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <RT-Ticket-46182@linuxfoundation>
2017-09-25  0:03 ` Linux 4.14-rc2 Linus Torvalds
2017-09-25  2:57   ` Linux 4.14-rc2 (bad patch file on kernel.org) Randy Dunlap
2017-09-25  3:41     ` Linus Torvalds
2017-09-25  3:41       ` [Kernel.org Helpdesk #46182] [linuxfoundation.org #46182] " Linus Torvalds via RT
2017-09-25  3:43       ` Linus Torvalds
2017-09-25  3:43         ` Linus Torvalds via RT [this message]
2017-10-15  6:58         ` Pavel Machek
2017-10-15 21:59           ` [Kernel.org Helpdesk #46182] [linuxfoundation.org #46182] " Pavel Machek via RT
2017-09-25 13:16     ` [Kernel.org Helpdesk " Konstantin Ryabitsev via RT

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=rt-4.4.0-6214-1506311032-730.46182-6-0@linuxfoundation \
    --to=kernel-helpdesk@rt.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.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

all inboxes | Powered by JetHome®