From: Dan Kegel <dank@kegel.com>
To: cygwin@cygwin.com
Subject: Re: how to allow connections from another host to cygwin
Date: Tue, 02 Jul 2013 02:07:00 -0000 [thread overview]
Message-ID: <CAPF-yOY06Cd3KmVQH2BCZx_7yVVNyomMiftnbEg+hG5mALRW=A@mail.gmail.com> (raw)
In-Reply-To: <20130702003405.GA6904@ednor.casa.cgf.cx>
On Mon, Jul 1, 2013 at 5:34 PM, Christopher Faylor wrote:
> If you've followed this mailing list for any length of time you'd notice
> that we don't really endorse the instructions from random other web
> sites. They are often out-of-date and contain needless instructions.
What's the prevailing thought on a wiki (presumably one
set up like the glibc one, by invite only, to avoid spammers)?
I found various posts on this list over the years, but no
obvious interest.
> Just use the instructions from /usr/share/doc/Cygwin/openssh.README
That file is not very easily discovered (despite the FAQ entry
that explains that convention). Can you add a link to
an static index of all those files from http://cygwin.com/docs.html ?
That might make googling
openssh server cygwin
more likely to find it.
Hrmph, just found http://sshwindows.sourceforge.net/
That just seems wrong...
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2013-07-02 2:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 22:15 markov
2013-07-01 23:08 ` Dan Kegel
2013-07-02 0:34 ` Christopher Faylor
2013-07-02 2:07 ` Dan Kegel [this message]
2013-07-02 8:19 ` Corinna Vinschen
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='CAPF-yOY06Cd3KmVQH2BCZx_7yVVNyomMiftnbEg+hG5mALRW=A@mail.gmail.com' \
--to=dank@kegel.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).