From: norman@oclsc.org (Norman Wilson)
Subject: [TUHS] Excessive bouncing ... argh!
Date: Sat, 23 Sep 2017 11:54:08 -0400 [thread overview]
Message-ID: <1506182054.27729.for-standards-violators@oclsc.org> (raw)
Tom Ivar Helbekkmo:
Why should anyone need to? Of all the mailing lists I'm on, this one is
the only one that has this problem.
=====
Beware tunnel vision. Another mailing list I'm on has exactly
the same problem, made worse because it's being run by a central
Big Company Mailing List Provider so the rules keep changing under
foot and it's up to the poor-sod list maintainer (who is not a
programmer) to cope.
To bring the focus back to this mailing list, not every program
runs on a little-endian computer with arbitrary word alignment
and pointers that fit in an int.
Norman Wilson
Toronto ON
next reply other threads:[~2017-09-23 15:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-23 15:54 Norman Wilson [this message]
2017-09-23 16:18 ` Tom Ivar Helbekkmo
2017-09-23 20:02 ` Grant Taylor
-- strict thread matches above, loose matches on Subject: below --
2017-09-21 22:34 Warren Toomey
2017-09-22 11:46 ` Steffen Nurpmeso
2017-09-22 19:51 ` Grant Taylor
2017-09-23 14:07 ` Theodore Ts'o
2017-09-23 18:17 ` Lyndon Nerenberg
2017-09-23 18:35 ` Tom Ivar Helbekkmo
2017-09-22 20:09 ` Gregg Levine
2017-09-23 7:50 ` Tom Ivar Helbekkmo
2017-09-23 9:05 ` Grant Taylor
2017-09-23 14:12 ` Theodore Ts'o
2017-09-23 14:57 ` Tom Ivar Helbekkmo
2017-09-23 16:27 ` Ian Zimmerman
2017-09-23 15:41 ` Ian Zimmerman
2017-09-23 20:24 ` Grant Taylor
2017-09-24 0:03 ` Random832
2017-09-24 6:52 ` Tom Ivar Helbekkmo
2017-09-23 22:27 ` Dave Horsfall
2017-09-24 22:32 ` Derek Fawcus
2017-09-24 23:43 ` Dave Horsfall
2017-09-25 16:50 ` Ian Zimmerman
2017-09-26 4:19 ` Dave Horsfall
2017-09-26 5:30 ` Tom Ivar Helbekkmo
2017-09-26 14:32 ` Gregg Levine
2017-09-26 16:00 ` Ralph Corderoy
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=1506182054.27729.for-standards-violators@oclsc.org \
--to=norman@oclsc.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).