From: geoff@collyer.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: Stitch and EFIS
Date: Thu, 2 Feb 2006 00:45:51 -0800 [thread overview]
Message-ID: <efe659f3916e9ba099ee12b96a02ce21@collyer.net> (raw)
In-Reply-To: <0df4a3400e775c9a116de76c84aa1d1d@cat-v.org>
You should be able to search the archives, even if just with grep or
google.
Somebody might fix a broken program left lying around, but it hasn't
happened often, in my experience, and it's more likely to frustrate
people when they find that it's broken.
I can't help with EFIS.
next prev parent reply other threads:[~2006-02-02 8:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-01 11:08 [9fans] " uriel
2006-02-01 17:18 ` [9fans] " Dave Eckhardt
2006-02-02 2:08 ` geoff
2006-02-02 6:37 ` Dan Cross
2006-02-02 8:28 ` uriel
2006-02-02 8:33 ` geoff
2006-02-02 8:39 ` uriel
2006-02-02 8:45 ` geoff [this message]
2006-02-02 14:43 ` Sascha Retzki
2006-02-03 0:04 ` geoff
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=efe659f3916e9ba099ee12b96a02ce21@collyer.net \
--to=geoff@collyer.net \
--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).