From: Stas Sergeev <stssppnn@yahoo.com>
To: linux-msdos@vger.kernel.org
Subject: Re: ugetcwd / uchdir freakiness
Date: Tue, 22 Apr 2003 03:08:51 +0400 [thread overview]
Message-ID: <3EA47A03.4040509@yahoo.com> (raw)
Hello.
"Bart Oldeman" <bart.oldeman@bristol.ac.uk> wrote:
>> I think sooner or later we'll have
>> to return back to the known-good
>> standalone-style tools:(
> the problem with those (well partly) is that we'd need to rely on third
> party compilers ("invoke tcc via dosemu").
That's why I have put a backward smiley there.
I mean it would no doubt be much better
to keep using the builtin ones, and to
get rid of all the problems alltogether
only the comcom must be dropped in favour
of the much better FreeCOM. If this is
done, besides getting rid of all the
comcom's problems, 4/5 of the convoluted
coopthreads code can be simply thrown away
and the rest can be greately simplified.
next reply other threads:[~2003-04-21 23:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-21 23:08 Stas Sergeev [this message]
2003-04-22 1:00 ` ugetcwd / uchdir freakiness Bart Oldeman
-- strict thread matches above, loose matches on Subject: below --
2003-04-22 10:13 Stas Sergeev
2003-04-21 16:39 Stas Sergeev
2003-04-21 21:44 ` Bart Oldeman
2003-04-17 10:09 Pawel Szymczykowski
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=3EA47A03.4040509@yahoo.com \
--to=stssppnn@yahoo.com \
--cc=linux-msdos@vger.kernel.org \
/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