From: Oleksandr Gavenko <gavenkoa@gmail.com>
To: cygwin@cygwin.com
Subject: Suggestion to move Cygwin documentation to more version neutral path...
Date: Sun, 29 May 2016 01:40:00 -0000 [thread overview]
Message-ID: <87lh2t3mk7.fsf@gavenkoa.example.com> (raw)
I search for bundled docs to set up sshd and some mount points and surprised
that it placed on path:
/usr/share/doc/cygwin-2.5.1/html/cygwin-ug-net
As far as I know current Cygwin version is 1.7.
With "cygwin-2.5.1" part I begin to doubt if docs is up-to-date.
So I consult online docs because be unsure if it is actual.
Can we have /usr/share/doc/cygwin-2.5.1 with names like:
/usr/share/doc/cygwin-1.7
or:
/usr/share/doc/cygwin-current
or whatever better.
I see /usr/share/doc/Cygwin already have special purpose...
--
http://defun.work/
--
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 reply other threads:[~2016-05-28 21:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-29 1:40 Oleksandr Gavenko [this message]
2016-05-29 6:41 ` Hans-Bernhard Bröker
2016-05-29 15:19 ` Oleksandr Gavenko
2016-05-29 18:30 ` Andrey Repin
2016-05-30 14:53 ` Oleksandr Gavenko
2016-05-30 16: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=87lh2t3mk7.fsf@gavenkoa.example.com \
--to=gavenkoa@gmail.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).