linux-assembly.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maciej Hrebien <m_hrebien@wp.pl>
To: linux-assembly@vger.kernel.org
Subject: Re: The Well-Factored 386
Date: Tue, 29 Jul 2003 18:49:12 +0200	[thread overview]
Message-ID: <3F26A588.EB8DA4D5@wp.pl> (raw)
In-Reply-To: 16165.48414.123242.660524@eidolon.muppetlabs.com

Brian Raiter wrote:
> 
> > Rick, I wish you luck finding another machine with lists to
> > infiltrate.
> >
> > Because you're not going to do it on vger.kernel.org any more.
> > Bye bye.
> 
> I've no doubt that his posts seemed off-topic for linux-kernel, I
> would argue that they are certainly on-topic for linux-assembly. (I
> also imagine the latter sees much less traffic than the former, thus
> hp's comment.) I rather doubt that the complaints were coming from
> both lists, given that his stuff is far more interesting that the
> usual linux-assembly posts ("how do I write a number to screen without
> using BIOS?!") Assuming this is true, perhaps it would make more sense
> to allow him to continue posting to linux-assembly?

I agree with Brian & hp. I find quite interesting what Rick is writing
rather than reading another question & another answer that you can find
in mail archives or just by tring to "research" the answer by yourself.
True, maybe it's not for linux-kernel but David! let him post on
linux-assembly. Konst's linuxassembly.org/list.html has:

[ ... ]

Discuss it at the Linux Assembly Programming mailing list! 

     This is an open discussion of assembly programming under Linux,
*BSD, BeOS, or any other UNIX/POSIX like OS; also it is not limited to
x86 assembly
     (Alpha, Sparc, PPC and other hackers are welcome too!). 

                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

     Before asking a question, please search list archives first; it is
fairly possible that an answer is already there. 

[ ... ]

David, he speaks around the list main topic i think, it's quite
interesting, maybe not all (for me!), but more useful then "please help
me" postings. He doesn't commercials, non-censored or other stupid
things. Let him talk about his bash-assembly & other projects with
connection to the topic.

BTW: how many people from linux-assembly complainted Rick? Could you
give as this information? Or some proportions lx-as vs lx-ker?

-- 
Maciej Hrebien


  reply	other threads:[~2003-07-29 16:49 UTC|newest]

Thread overview: 15+ 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
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  8:45           ` hp
2003-07-28 23:11         ` viro
2003-07-29  0:17       ` Brian Raiter
2003-07-29 16:49         ` Maciej Hrebien [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-29 21:41 The well-factored 386 Jack Dennon

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=3F26A588.EB8DA4D5@wp.pl \
    --to=m_hrebien@wp.pl \
    --cc=linux-assembly@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 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).