From: pat@picoworks.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] troff
Date: Sat, 3 Jul 2004 22:34:49 -0700 [thread overview]
Message-ID: <9faedf4b49a62db080104d29cd1db805@picoworks.com> (raw)
In-Reply-To: <003a01c46187$cd536390$de597d50@SOMA>
[-- Attachment #1: Type: text/plain, Size: 33 bytes --]
.tl 'left 'center'right'
Pat
[-- Attachment #2: Type: message/rfc822, Size: 2468 bytes --]
From: "boyd, rounin" <boyd@insultant.net>
To: <9fans@cse.psu.edu>
Subject: [9fans] troff
Date: Sun, 4 Jul 2004 07:28:50 +0200
Message-ID: <003a01c46187$cd536390$de597d50@SOMA>
me getting old and that, i forget what a 3 part title is/was:
.tr
maybe?
--
MGRS 31U DQ 52572 12604
prev parent reply other threads:[~2004-07-04 5:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-04 5:28 boyd, rounin
2004-07-04 5:34 ` pat [this message]
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=9faedf4b49a62db080104d29cd1db805@picoworks.com \
--to=pat@picoworks.com \
--cc=9fans@cse.psu.edu \
/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).