From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Managing kernel-updates in rpm
Date: Tue, 25 Mar 2014 07:07:19 -0700 [thread overview]
Message-ID: <20140325140719.GC16994@kroah.com> (raw)
In-Reply-To: <40146.1395754331@turing-police.cc.vt.edu>
On Tue, Mar 25, 2014 at 09:32:11AM -0400, Valdis.Kletnieks at vt.edu wrote:
> On Tue, 25 Mar 2014 18:18:35 +0530, Saket Sinha said:
>
> > Its a proprietary driver so its not meant to be the part of
> > mainline kernel. :(
>
> Hey Greg - how long did Linux carry around an entire freaking *architecture*
> for the Voyager when there were only like 4 systems on the *planet* still in
> existence?
There was only 1 working system, and it was years :)
next prev parent reply other threads:[~2014-03-25 14:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 7:24 Managing kernel-updates in rpm Saket Sinha
2014-03-25 8:39 ` parinay
2014-03-25 9:02 ` Saket Sinha
2014-03-25 12:42 ` Greg KH
2014-03-25 12:48 ` Saket Sinha
2014-03-25 13:32 ` Valdis.Kletnieks at vt.edu
2014-03-25 14:07 ` Greg KH [this message]
2014-03-25 14:06 ` Greg KH
2014-03-25 13:27 ` Valdis.Kletnieks at vt.edu
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=20140325140719.GC16994@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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).