From: Thomas Gleixner <tglx@linutronix.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: PEBTAO [ was Re: [ANNOUNCE] 3.0.6-rt17 ]
Date: Sat, 8 Oct 2011 01:14:11 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1110080010000.3240@ionos> (raw)
In-Reply-To: <b11eac52-79af-40ea-a53b-6f77581be035@email.android.com>
On Fri, 7 Oct 2011, Steven Rostedt wrote:
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> Nice work Thomas!
>
> -- Steve
> --
> Sent from my Android phone with K-9 Mail. Please excuse my brevity.
This sig is obviously a total failure. Brevity would have been a
mail with a single line saying: "Nice work Thomas!"
If you insist on having a sig, then please change it to something
sensible like:
"This affront against netiquette is caused by PEBTAO"
PEBTAO is the Web 2.0 advancement of PEBKAC:
Problem Exists Between Touchscreen and Occiput
I know that you just wanted to taunt me after our IRC conversation,
but seriously the amount of horribly formatted mails on LKML starts to
be annoying.
If it would be only the "Sent from my .* phone" mails, it would be
easy to filter out in .procmailrc. The bad news is that this habit of
top posting and miserable quoting spreads like cancer and I have no
intention to cope with that anymore. Having to scroll down several
pages to find the content (if any) of a reply is equally annoying as
reading a top post with no context.
Darn, email is our main communication medium even if some people
think, that discussions on farcebook or gurgle+ are way better.
I don't care whether this new, hip form of communication is considered
cool and used in private or corporate context, but I care very much
about the sanity of my personal workflow and the efficiency of the
proven model.
A well considered N days delayed reply is way more worth than some
hastily cobbled together .*phone message which just proves that the
person owns such a thing and is permanentely "available".
Can we please go back to the established working model of keeping
stuff on mailing lists and follow the well established netiquette
instead of spreading those absurdities?
Thanks,
tglx
next prev parent reply other threads:[~2011-10-07 23:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-07 1:15 [ANNOUNCE] 3.0.6-rt17 Thomas Gleixner
2011-10-07 1:20 ` Madovsky
2011-10-07 1:52 ` Luis Claudio R. Goncalves
2011-10-07 4:13 ` Frank Rowand
2011-10-07 8:10 ` Rolando Martins
2011-10-07 17:25 ` Fernando Lopez-Lezcano
2011-10-07 19:54 ` Fernando Lopez-Lezcano
2011-10-07 22:02 ` Thomas Gleixner
2011-10-07 23:05 ` Fernando Lopez-Lezcano
2011-10-13 7:52 ` [PATCH -rt] hrtimer: Add missing debug_activate() aid [Was: Re: [ANNOUNCE] 3.0.6-rt17] Yong Zhang
[not found] ` <b11eac52-79af-40ea-a53b-6f77581be035@email.android.com>
2011-10-07 23:14 ` Thomas Gleixner [this message]
2011-10-07 23:25 ` PEBTAO [ was Re: [ANNOUNCE] 3.0.6-rt17 ] Steven Rostedt
2011-10-07 23:30 ` Thomas Gleixner
2011-10-08 0:26 ` Valdis.Kletnieks
2011-10-08 7:56 ` octoploid
2011-10-08 11:26 ` Serieal console on Samsung S3C6410 ARM11 CPU (Was [ANNOUNCE] 3.0.6-rt17) Juergen Beisert
2011-10-08 13:29 ` Thomas Abraham
2011-10-08 18:15 ` Juergen Beisert
2011-10-08 19:01 ` Thomas Abraham
2011-10-08 20:56 ` [ANNOUNCE] 3.0.6-rt17 Maarten Lankhorst
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=alpine.LFD.2.02.1110080010000.3240@ionos \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.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).