From: Linus Torvalds <torvalds@linux-foundation.org>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: Linux 3.10-rc4
Date: Mon, 3 Jun 2013 18:19:20 +0900 (PWT) [thread overview]
Message-ID: <alpine.LFD.2.03.1306031815400.21004@pixel.linux-foundation.org> (raw)
In-Reply-To: <20908.23892.888385.996094@pilspetsen.it.uu.se>
On Mon, 3 Jun 2013, Mikael Pettersson wrote:
> Randy Dunlap writes:
> >
> > I still use tarballs and patches, fwiw.
>
> As do I. For this one time the lack of a patch file is no big deal, but
> please don't discontinue them permanently.
The tar-ball is now there, courtesy of Konstantin. No patch-file, though.
And I won't discontinue the tar-balls/patch-files as long as there are
users. At least not in the near future.
Linus
prev parent reply other threads:[~2013-06-03 9:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-02 8:45 Linux 3.10-rc4 Linus Torvalds
2013-06-02 18:39 ` Randy Dunlap
2013-06-03 9:09 ` Mikael Pettersson
2013-06-03 9:19 ` Linus Torvalds [this message]
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=alpine.LFD.2.03.1306031815400.21004@pixel.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--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