From: hp <lx@lxhp.in-berlin.de>
To: "David S. Miller" <davem@redhat.com>,
"Rick A. Hohensee" <rickh@capaccess.org>
Cc: linux-kernel@vger.kernel.org, linux-assembly@vger.kernel.org
Subject: Re: The Well-Factored 386
Date: Mon, 28 Jul 2003 17:36:10 +0100 [thread overview]
Message-ID: <200307281736.10510.lx@lxhp.in-berlin.de> (raw)
In-Reply-To: <20030728070658.343ed2b0.davem@redhat.com>
though probably not always that enlightning as announced, I certainly would
not consider those artices 'off topic'. - i fact, despite i don't understand
a word of those silly idiomatic texts, sometimes, i found the latest one
quite interesting and, tightly reated to 'assembly' . any attempt to trying
to documenting on the rsp. cpu should be regarded "on-topic", what else...!
and, no #reader# (as opposed to some until now un-known, sort of 'maintainer')
seems to have felt offended so there is no reason to that rude admonition.
for instance, i would find those overly repeated, stupid questions about some
obscure 'real mode' in linux (or for access to #the# graphic memory) much
more annoying and accordinly "off topic" - if i would, at all.
or, were you trying to cut down a bit on the tremendous traffic in this group?
what a great relief...
thanks + regards,
hp
David S. Miller am Montag, 28. Juli 2003 15:06:
> On Mon, 28 Jul 2003 04:44:56 -0400
>
> "Rick A. Hohensee" <rickh@capaccess.org> wrote:
> > The four actual main modes of the 386
>
> Please stop making off-topic postings. If you continue to do
> so I will have to yank you from the lists at vger.kernel.org
> and filter you from sending emails to the lists.
>
> Thank you.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-assembly"
> in the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Linux,Assembly,Forth: http://www.lxhp.in-berlin.de/index-lx.shtml en/de
FAQ(s) + DOCs at http://linuxassembly.org
pse, reply to << lx -at- lxhp -dot- in-berlin -dot- de >>
next prev parent reply other threads:[~2003-07-28 15:21 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 8:44 The Well-Factored 386 Rick A. Hohensee
2003-07-28 14:06 ` David S. Miller
2003-07-28 16:36 ` hp [this message]
2003-07-28 20:33 ` Rick A. Hohensee
2003-07-28 20:33 ` David S. Miller
2003-07-28 22:27 ` Stephan von Krawczynski
2003-07-28 22:30 ` David S. Miller
2003-07-28 22:58 ` David D. Hagood
2003-07-29 14:32 ` Timothy Miller
2003-07-29 17:21 ` hp
2003-07-29 0:34 ` jw schultz
2003-07-29 1:27 ` Alan Cox
2003-07-29 3:49 ` Larry McVoy
2003-07-29 4:25 ` Gene Heskett
2003-07-29 4:42 ` jw schultz
2003-07-29 12:04 ` Alan Cox
2003-07-29 14:55 ` Timothy Miller
2003-07-29 8:45 ` hp
2003-07-28 23:11 ` viro
2003-07-29 0:17 ` Brian Raiter
2003-07-28 16:02 The well-factored 386 Jack Dennon
2003-07-28 16:32 ` David S. Miller
2003-07-28 16:46 ` Andries Brouwer
2003-07-28 16:55 ` David S. Miller
2003-07-28 19:31 ` Herbert Pötzl
2003-07-28 19:41 ` Jamie Lokier
2003-07-29 11:14 ` Helge Hafting
2003-07-29 16:19 ` Jamie Lokier
2003-07-30 7:11 ` Helge Hafting
2003-07-30 14:05 ` Jamie Lokier
2003-07-29 12:59 John Bradford
2003-07-29 13:32 ` Ville Herva
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=200307281736.10510.lx@lxhp.in-berlin.de \
--to=lx@lxhp.in-berlin.de \
--cc=davem@redhat.com \
--cc=linux-assembly@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rickh@capaccess.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).