From: anothy@cosym.net
To: 9fans@cse.psu.edu
Subject: Re:[9fans] image resampling
Date: Mon, 15 Apr 2002 13:20:56 -0400 [thread overview]
Message-ID: <20020415172102.F01AE19A2C@mail.cse.psu.edu> (raw)
//But trying to track down all the bugs made my brain freeze...
is this "because there were so many and it's tedious, involved
work" or "because they were really complicated and dificult to
track down"? if the later, i probably don't even want to _look_
at the code. but if the former, could maybe some of us help
with that? i've longed for various tools from the fb suite many
times now, and would be interested in helping to get them out
under the 3rd edition (i've got a 2nd edition license, but have
lost my CD, and am not as excited about doing this sort of
work if i can't share it with people). would it be possible to
release however far you got, or even the now-fully-obsolete
2nd edition fb suite, under the current license?
ア
next reply other threads:[~2002-04-15 17:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-15 17:20 anothy [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-15 17:38 rob pike, esq.
2002-04-15 17:20 rog
2002-04-15 16:32 rob pike, esq.
2002-04-15 15:57 rog
2002-04-15 15:33 rob pike, esq.
2002-04-15 15:26 rog
2002-04-15 9:39 steve.simon
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=20020415172102.F01AE19A2C@mail.cse.psu.edu \
--to=anothy@cosym.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).