From: rh_ <richard_hubbe11@lavabit.com>
To: linux-kernel@vger.kernel.org
Subject: Re: apparent loss of continuity in kernel .config?
Date: Fri, 2 Jan 2015 08:59:52 -0800 [thread overview]
Message-ID: <20150102085952.27a7ce3b@127> (raw)
In-Reply-To: 201501011843.03418.gheskett@wdtv.com
On Thu, 1 Jan 2015 18:43:03 -0500
Gene Heskett <gheskett@wdtv.com> wrote:
>
> IMO that is NOT how its supposed to work. So I guess I'll waste a
I agree.
> tree and print a working 3.16.0 & use that to build a new one. I do
> not believe it even makes an attempt to read the old one, but simply
> goes wandering in the vineyard, making frequent stops to recycle the
> barrel sampling.
I used to try to make it work but I usually give up and stick with
the config that works. Maybe I'm doing it all wrong. My laptop works
fine though. But it wasn't easy building a static kernel for it.
>
> Indeed, but it no doubt will take quite a few boxes. The funny thing
Probably true.
> lots of people find hard to believe is that Ed wrote that in about
> 1940. His long view obviously started before mine as mine didn't
> start will late in '34. It took me till the middle 60's to decide
> its broken. And every libtard fix breaks it worse...
Smedley Butler and lots of others knew a long time ago too.
G.E. Griffin and friends have lots to say.
The long-con is always hard to see.
>
>
> Thanks & lets hope 2015 is a better year.
Can do.
>
> Cheers, Gene Heskett
> --
> "There are four boxes to be used in defense of liberty:
> soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> Genes Web page <http://geneslinuxbox.net:6309/gene>
> US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS
next prev parent reply other threads:[~2015-01-02 17:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-31 14:16 apparent loss of continuity in kernel .config? Gene Heskett
2015-01-01 19:24 ` rh_
2015-01-01 23:43 ` Gene Heskett
2015-01-02 16:59 ` rh_ [this message]
2015-01-02 9:31 ` Geert Uytterhoeven
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=20150102085952.27a7ce3b@127 \
--to=richard_hubbe11@lavabit.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.