From: "Andrey S. Kukhar" <plan9@kp.km.ua>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Marsv presentation at Houston
Date: Fri, 7 Feb 2003 19:48:16 -0500 [thread overview]
Message-ID: <03020719481601.00507@localhost.localdomain> (raw)
In-Reply-To: <f81d9348abe64c294453c97ccd5d1a2c@granite.cias.osakafu-u.ac.jp>
is marsv soft available online?
-kyxap
> > We will make presentation of our marsv software
> > (previously Planv) at Houston March, the abstract of
> > which is seen at
>
> Huuu,,,,
>
> I think I got fix of the major bug of it!
> Using channel is not so easy when we have to deel with
> large deeply nested thread.
>
> Sorry, to bother all, I've been struggling against this
> for about a month. Yes, I'm not a good programmer, but
> just a geologist...
>
> Kenji
next prev parent reply other threads:[~2003-02-08 0:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-07 9:38 okamoto
2003-02-08 0:48 ` Andrey S. Kukhar [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-11 3:59 okamoto
2003-02-11 3:56 okamoto
2003-02-10 1:23 okamoto
2003-02-10 0:58 okamoto
2003-01-28 4:28 okamoto
2003-01-28 1:13 okamoto
2003-01-28 1:10 okamoto
2003-01-28 4:16 ` Jim Choate
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=03020719481601.00507@localhost.localdomain \
--to=plan9@kp.km.ua \
--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).