From: Al Viro <viro@ftp.linux.org.uk>
To: Marc Perkel <mperkel@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: The vi editor causes brain damage
Date: Sun, 19 Aug 2007 07:15:24 +0100 [thread overview]
Message-ID: <20070819061524.GT21089@ftp.linux.org.uk> (raw)
In-Reply-To: <964583.28477.qm@web52504.mail.re2.yahoo.com>
On Sat, Aug 18, 2007 at 10:20:34PM -0700, Marc Perkel wrote:
> Let me give you and example of the difference between
> Linux open source world brain damaged thinking and
> what it's like out here in the real world.
[snip]
Marc, why don't you do the obvious thing and hire Jeff Merkey?
He used to work on netware kernel, you are a netware fanboy...
Hell, he might even share - his peyotl for whatever you are on;
it certainly has... intriguing effects, so who knows - maybe the
mix will give the right kind of out-of-box experience for you ;-)
next prev parent reply other threads:[~2007-08-19 6:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-19 5:20 The vi editor causes brain damage Marc Perkel
2007-08-19 6:15 ` Al Viro [this message]
2007-08-19 6:29 ` Marc Perkel
2007-08-19 4:24 ` hotmetal
2007-08-19 13:07 ` Marc Perkel
2007-08-19 7:15 ` Jiri Slaby
2007-08-19 7:21 ` [OT] " Willy Tarreau
2007-08-19 12:31 ` Benny Amorsen
2007-08-19 12:39 ` Paolo Ornati
2007-08-19 13:07 ` variable length argument support (was: [OT] Re: The vi editor causes brain damage) Jan Engelhardt
2007-08-19 14:40 ` Paolo Ornati
2007-08-19 13:22 ` The vi editor causes brain damage Marc Perkel
2007-08-19 13:33 ` Willy Tarreau
2007-08-19 14:06 ` Jose Celestino
2007-08-19 14:48 ` Paolo Ornati
2007-08-19 15:32 ` Marc Perkel
2007-08-19 17:32 ` Arjan van de Ven
2007-08-19 23:03 ` Michael Tharp
2007-08-20 1:55 ` Casey Dahlin
2007-08-19 13:55 ` [OT] " Torsten Duwe
2007-08-19 13:08 ` Marc Perkel
2007-08-19 20:14 ` Valdis.Kletnieks
-- strict thread matches above, loose matches on Subject: below --
2007-08-20 9:41 Tim Tassonis
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=20070819061524.GT21089@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mperkel@yahoo.com \
/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.