public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Joel Rees <joel.rees@gmail.com>
Cc: Gregory Smith <gregorysmith1974a@gmail.com>,
	debian-user <debian-user@lists.debian.org>,
	linux-kernel@vger.kernel.org
Subject: Re: sock puppets (Re: (Song) ** SystemD)
Date: Mon, 6 Oct 2014 00:35:42 +0100	[thread overview]
Message-ID: <20141005233542.GY7996@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAAr43iOesCSCCVDHBGdc=dNO5J3LgGzVabLusZ75ZhPtHmiyMg@mail.gmail.com>

On Mon, Oct 06, 2014 at 07:42:32AM +0900, Joel Rees wrote:
> I don't know which side you're on.
> 
> All I know is that with all the shock treatment from the noisiest part
> of the supposedly anti-crowd and the arrogance, lies, petulance,
> pretense, and other primadonna behavior that business-types seem to
> like from the pro-crowd, good engineering practices are being thrown
> overboard.
> 
> Your poisoning the conversation does not help promote good
> engineering, that should be obvious. So I tend to think you are a
> sock-puppet of the pro-crowd, maybe even Sievers or Poettering posting
> under an alias.

You are overcomplicating it.  More likely s/h/it doesn't give a flying fuck
about the outcome, provided that its worthless self gets attention along
the way...

On the off-chance that original poster might someday have a point on something:
	a) You are not Luis Buñuel.  You are not even Ed Wood.
	b) If plain text isn't convincing, throwing video and audio into the
mix won't improve it.
	c) If you can't get through that without rambling, write it down and
trim the crap out.  On related note, if you are recording something and feel
that you need to take a good dump, put the recording on pause.  Rationale: (a).

  parent reply	other threads:[~2014-10-05 23:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-05 13:51 sock puppets (Re: (Song) ** SystemD) Joel Rees
2014-10-05 21:15 ` Gregory Smith
2014-10-05 21:58   ` Ken Moffat
2014-10-05 22:42   ` Joel Rees
2014-10-05 23:06     ` Gregory Smith
2014-10-05 23:35     ` Al Viro [this message]
2014-10-06  0:15       ` Gregory Smith
     [not found]         ` <CAAr43iOugvZSsOO=J+yRkq25TyNmQG6CfwjtKCQuFx=uV5Mq=A@mail.gmail.com>
2014-10-06  3:42           ` Gregory Smith
     [not found]         ` <20141006024914.GZ7996@ZenIV.linux.org.uk>
     [not found]           ` <CALtyatEXvZo27fe1X2UGTAwZGgy1+Jwpm1j7_=8QQM68nnBVfA@mail.gmail.com>
     [not found]             ` <20141006050938.GC7996@ZenIV.linux.org.uk>
2014-10-06  5:29               ` Gregory Smith
2014-10-06  6:06                 ` Al Viro
2014-10-06 11:15                   ` Gregory Smith

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=20141005233542.GY7996@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=debian-user@lists.debian.org \
    --cc=gregorysmith1974a@gmail.com \
    --cc=joel.rees@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