From: Marc Perkel <mperkel@yahoo.com>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: The vi editor causes brain damage
Date: Sun, 19 Aug 2007 06:08:07 -0700 (PDT) [thread overview]
Message-ID: <782674.68281.qm@web52502.mail.re2.yahoo.com> (raw)
In-Reply-To: <46C7EE0A.2030601@gmail.com>
--- Jiri Slaby <jirislaby@gmail.com> wrote:
> Marc Perkel napsal(a):
> > 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.
> >
> > Go to a directory with 10k files and type:
> >
> > rm *
> >
> > What do you get?
> >
> > /bin/rm: Argument list too long
>
> What does this have to do with rm command?
>
See what I mean?
Marc Perkel
Junk Email Filter dot com
http://www.junkemailfilter.com
____________________________________________________________________________________
Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase.
http://farechase.yahoo.com/
next prev parent reply other threads:[~2007-08-19 13:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-19 5:20 Marc Perkel
2007-08-19 6:15 ` Al Viro
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 [this message]
2007-08-19 20:14 ` Valdis.Kletnieks
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=782674.68281.qm@web52502.mail.re2.yahoo.com \
--to=mperkel@yahoo.com \
--cc=jirislaby@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome