From: Stas Sergeev <stsp@aknet.ru>
To: linux-msdos@vger.kernel.org
Subject: Re: 1.0.2.1 and latest kernel?a [1.1.5.7 now]
Date: Thu, 18 Sep 2003 23:22:14 +0400 [thread overview]
Message-ID: <3F6A05E6.3050801@aknet.ru> (raw)
Hello.
Ryan Underwood wrote:
> Ryans Todo List: - slowdown kludges - document telnetting to dosemu
> application on inetd - update Win3.11-DOSEMU HOWTO
> What are some other stuff that needs to be worked on
Yes, as the work on 1.2-stable branch is
started, the doc updates are rather important
I think. Good that you took the Win3.11 part,
I am removing it from my "to-do for 1.2" then.
Any other doc updates might also be appreciated.
>> "seen". I grepped through the docs for "lexer" and "parser" but
>> didn't see much useful right away.
> I take it from lack of response that nobody knows? :)
No, it is just that without a detailed description,
without showing your changes and without any info
at all, asking for the hints is a sure way to be
left unanswered:) (and you can find an examples of
such a patches everywhere around)
next reply other threads:[~2003-09-18 19:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 19:22 Stas Sergeev [this message]
2003-09-18 23:42 ` 1.0.2.1 and latest kernel?a [1.1.5.7 now] Bart Oldeman
2003-09-19 5:30 ` Ryan Underwood
2003-09-19 2:05 ` Ryan Underwood
-- strict thread matches above, loose matches on Subject: below --
2003-09-16 3:29 1.0.2.1 and latest kernel? Stas Sergeev
2003-09-16 3:51 ` Ryan Underwood
2003-09-16 9:05 ` 1.0.2.1 and latest kernel?a [1.1.5.7 now] Ryan Underwood
2003-09-16 9:12 ` Bart Oldeman
2003-09-16 9:21 ` Ryan Underwood
2003-09-16 9:33 ` Ryan Underwood
2003-09-18 9:07 ` Ryan Underwood
2003-09-18 11:52 ` Bart Oldeman
2003-09-18 12:50 ` Ryan Underwood
2003-09-19 4:26 ` Ryan Underwood
2003-09-19 5:08 ` Ryan Underwood
2003-09-19 9:30 ` Bart Oldeman
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=3F6A05E6.3050801@aknet.ru \
--to=stsp@aknet.ru \
--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