From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: The Cygwin Server Daemon - VERY LONG
Date: Tue, 23 Apr 2002 02:12:00 -0000 [thread overview]
Message-ID: <20020423105435.I7762@cygbert.vinschen.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0204222205060.9968-100000@fs1.in>
On Mon, Apr 22, 2002 at 10:44:27PM -0700, Richard Troy wrote:
> Commentary? Anybody know where there's a reasonably concise write up of
> this strategy?
There are several "how-*.txt" file in the cygwin source dir. Perhaps
these are a bit of a help.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:cygwin@cygwin.com
Red Hat, Inc.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2002-04-23 8:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 13:31 Richard Troy
2002-04-22 18:49 ` The Cygwin Server Daemon Richard Troy
2002-04-22 22:50 ` The Cygwin Server Daemon - VERY LONG Richard Troy
2002-04-23 2:12 ` Corinna Vinschen [this message]
2002-04-23 4:33 Robert Collins
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=20020423105435.I7762@cygbert.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).