From: Stas Sergeev <stssppnn@yahoo.com>
To: linux-msdos@vger.kernel.org
Subject: Re: Seg fault after quitting FoxPro 6 app
Date: Fri, 20 Sep 2002 04:25:06 +0400 [thread overview]
Message-ID: <3D8A6AE2.4090603@yahoo.com> (raw)
Hello.
Bart Oldeman wrote:
>> Isn't 1.0.2.1 the latest 'stable' version,
>> whilst 1.1.3 is unstable' ?
> Yes.
Well, no:)
Consider this: 1.0.2.1 had enough *known* bugs
for too long. Version that have known bugs (in
contrast to unknown, which are always present)
can't be called "stable" or recommended for a
real use IMO, esp. when such bugs are many and
some are serious.
> It's basically like this:
> if 1.0.2.1 works for you then stick with it.
That's true but atleast every person must be aware
that this version have *known* bugs and there is
another version which doesn't have atleast those.
This is what most people not even suspect (but
for the readers of this list it is strange:)
next reply other threads:[~2002-09-20 0:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-20 0:25 Stas Sergeev [this message]
2002-09-20 0:57 ` Seg fault after quitting FoxPro 6 app Bart Oldeman
-- strict thread matches above, loose matches on Subject: below --
2002-09-19 21:33 Stas Sergeev
2002-09-19 21:52 ` Oscar A. Valdez
2002-09-19 22:33 ` Bart Oldeman
2002-09-19 20:34 Oscar A. Valdez
2002-09-20 4:07 ` Grigory Batalov
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=3D8A6AE2.4090603@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