From: arnold@skeeve.com
To: norman@oclsc.org, lm@mcvoy.com
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] SDB debugger
Date: Sun, 03 May 2020 01:14:02 -0600 [thread overview]
Message-ID: <202005030714.0437E2xv002086@freefriends.org> (raw)
In-Reply-To: <20200503024116.GE9534@mcvoy.com>
Larry McVoy <lm@mcvoy.com> wrote:
> I really don't know how systems people do it these days, it is a
> much more complex world.
>
> ... these days, I have no idea how I'd make a difference.
By doing something besides systems. There are tons of open source
projects at the user level that make a difference. Consider something
like AsciiDoc. Less than 10 years old (methinks), and in use for
production by at least one major technical publisher that I know of.
(And it sure beats the pants off of DocBook XML.)
Or the work I do on gawk, Chet on Bash, other GNU bits.
There's a whole world out there besides just the kernel.
Arnold
next prev parent reply other threads:[~2020-05-03 7:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-03 2:21 Norman Wilson
2020-05-03 2:41 ` Larry McVoy
2020-05-03 7:14 ` arnold [this message]
2020-05-03 3:05 ` Rob Pike
-- strict thread matches above, loose matches on Subject: below --
2020-05-02 2:52 Doug McIlroy
2020-05-02 17:45 ` Larry McVoy
2020-05-03 16:16 ` Rich Morin
2020-05-12 4:36 ` Dave Horsfall
2020-05-01 20:48 Paul Ruizendaal
2020-05-01 21:57 ` Clem Cole
2020-05-02 9:10 ` Paul Ruizendaal
2020-05-02 16:04 ` Clem Cole
2020-05-01 23:05 ` Jeremy C. Reed
2020-05-02 0:49 ` Noel Hunt
2020-05-02 1:22 ` Rob Pike
2020-05-02 3:49 ` Noel Hunt
2020-05-02 20:16 ` Paul Ruizendaal
2020-05-03 6:58 ` arnold
2020-05-03 16:13 ` Clem Cole
2020-05-03 16:53 ` Henry Bent
2020-05-03 17:06 ` Henry Bent
2020-05-03 17:13 ` Henry Bent
2020-05-03 20:26 ` Clem Cole
2020-05-03 17:35 ` Paul Winalski
2020-05-03 21:27 ` Paul Ruizendaal
2020-05-12 4:15 ` Dave Horsfall
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=202005030714.0437E2xv002086@freefriends.org \
--to=arnold@skeeve.com \
--cc=lm@mcvoy.com \
--cc=norman@oclsc.org \
--cc=tuhs@tuhs.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).