From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] idefs patch
Date: Wed, 15 Aug 2001 12:23:56 -0400 [thread overview]
Message-ID: <200108151623.MAA07446@augusta.math.psu.edu> (raw)
In-Reply-To: <3B7B316A.DED8096F@san.rr.com>
In article <3B7B316A.DED8096F@san.rr.com> you write:
>if you get it to work drop me a line. for some strange
>reason i can't build a working idefs any more without having
>it trash the free list during operation.
>
>what's stupid is that now that i sit here typing this i realize
>that i had not factored all the variables. maybe my _build_
>environment is bad. ugh.
Hadn't Nemo put some effort into merging the IDE patches into the current
file server code? I thought, for a time, that he was going to become the
keeper of the idefs code.... I'm not questioning your doing it Eric, of
course, but I'd hate to see a lot of duplication of effort.
- Dan C.
next prev parent reply other threads:[~2001-08-15 16:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-14 4:27 Eric Dorman
2001-08-14 13:17 ` Sam Ducksworth
2001-08-16 2:35 ` Eric Dorman
2001-08-15 16:23 ` Dan Cross [this message]
2001-08-16 13:18 ` Sam Ducksworth
2001-08-16 21:23 ` unknown
-- strict thread matches above, loose matches on Subject: below --
2001-08-13 23:08 Sam Ducksworth
2001-08-16 21:21 ` unknown
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=200108151623.MAA07446@augusta.math.psu.edu \
--to=cross@math.psu.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).