9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: William Josephson <jkw@eecs.harvard.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] troff port
Date: Sun, 16 May 2004 00:01:56 -0400	[thread overview]
Message-ID: <20040516040156.GA90538@mero.morphisms.net> (raw)
In-Reply-To: <ee9e417a04051516352281ba6f@mail.gmail.com>

On Sat, May 15, 2004 at 07:35:02PM -0400, Russ Cox wrote:
> I merged Taj's port into the CVS tree but it's
> marked as BUGGERED until someone gets rid
> of all the compilation warnings.

I'll merge in most of mine shortly since it is
more complete and the starter solenoid on my
car is toast so I'm not going anywhere without
an insulated screwdriver to short it out.


  parent reply	other threads:[~2004-05-16  4:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-15  6:44 Taj Khattra
2004-05-15 15:35 ` William Josephson
2004-05-15 23:35   ` Russ Cox
2004-05-15 23:38     ` boyd, rounin
2004-05-16  0:02       ` boyd, rounin
2004-05-16  4:01     ` William Josephson [this message]
2004-05-16  8:15     ` William Josephson

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=20040516040156.GA90538@mero.morphisms.net \
    --to=jkw@eecs.harvard.edu \
    --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).