The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: Dave Horsfall <dave@horsfall.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Whence did "XXX" come about?
Date: Thu, 3 Sep 2020 12:11:58 -0600	[thread overview]
Message-ID: <CANCZdfqk2e0vHJh_uF6d318=NYWq0DWjd-wMNjSO8jydJ+yz_w@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2009040325180.99359@aneurin.horsfall.org>

[-- Attachment #1: Type: text/plain, Size: 740 bytes --]

The earliest my quick grep could find was 4.0BSD. I didn't find it in this
sense in pwb, but it was a quick grep...

xxx is used extensively in prior versions, but there it's meaning is
'placeholder' or 'don't care'. Mostly for /tmp/XXXX files, but also for
things like Jxxx handles all the jump commands or dates of the form 24 Feb
XXXX or stuff like that.

Warner

On Thu, Sep 3, 2020 at 11:34 AM Dave Horsfall <dave@horsfall.org> wrote:

> For yonks I've been seeing "XXX" as a flag to mean "needs more work" or
> "look at this carefully, just in case" etc, and I use it myself.
>
> Whence did it come about?  I think I saw it as early as PWB, but can't be
> sure.
>
> -- Dave, wondering how many nanny-filters he triggered with "XXX"
>

[-- Attachment #2: Type: text/html, Size: 1176 bytes --]

  reply	other threads:[~2020-09-03 18:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-03 17:32 Dave Horsfall
2020-09-03 18:11 ` Warner Losh [this message]
2020-09-03 20:35   ` Warner Losh
2020-09-03 20:54     ` Dan Halbert
2020-09-03 22:13       ` Steve Nickolas
2020-09-04  3:02         ` Christopher Browne
2020-09-03 20:28 ` Warren Toomey

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='CANCZdfqk2e0vHJh_uF6d318=NYWq0DWjd-wMNjSO8jydJ+yz_w@mail.gmail.com' \
    --to=imp@bsdimp.com \
    --cc=dave@horsfall.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).