mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Torsten Duwe <duwe@lst.de>
To: Willy Tarreau <w@1wt.eu>
Cc: Jiri Slaby <jirislaby@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [OT] Re: The vi editor causes brain damage
Date: Sun, 19 Aug 2007 15:55:46 +0200	[thread overview]
Message-ID: <200708191555.46751.duwe@lst.de> (raw)
In-Reply-To: <20070819072135.GQ6002@1wt.eu>

On Sunday 19 August 2007, Willy Tarreau wrote:
> On Sun, Aug 19, 2007 at 09:15:22AM +0200, Jiri Slaby wrote:
> > What does this have to do with rm command?
> Nothing, and no more with linux development. Marc confuses shell and rm.

> (please do not follow up on this OT thread, responses to /dev/null)

Then do not answer in the first place. Do not answer at all. There's tons of 
good literature that explains this. Don't feed the troll.

	Torsten

  parent reply	other threads:[~2007-08-19 13:56 UTC|newest]

Thread overview: 22+ 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     ` Torsten Duwe [this message]
2007-08-19 13:08   ` Marc Perkel
2007-08-19 20:14 ` Valdis.Kletnieks

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=200708191555.46751.duwe@lst.de \
    --to=duwe@lst.de \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=w@1wt.eu \
    /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