From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Suggestion to move Cygwin documentation to more version neutral path...
Date: Mon, 30 May 2016 16:19:00 -0000 [thread overview]
Message-ID: <20160530093749.GA6659@calimero.vinschen.de> (raw)
In-Reply-To: <87vb1v28wr.fsf@gavenkoa.example.com>
[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]
On May 30 12:27, Oleksandr Gavenko wrote:
> On 2016-05-29, Andrey Repin wrote:
>
> > Why do you refer to last year's announce?
> > Why not https://cygwin.com/ml/cygwin-announce/2016-04/msg00063.html ?
>
> I finally got it.
>
> I made accidental assumptions and conclusions that led to misunderstanding.
>
> https://www.cygwin.com/ page is not so easy lead to
>
> https://cygwin.com/cygwin-ug-net/ov-new.html
> What's new and what changed in Cygwin
>
> which I want to see in first place.
Please feel free to suggest website changes and send matching patches.
The generic website stuff is under git:
https://cygwin.com/git/gitweb.cgi?p=cygwin-htdocs.git
The User's Guide, the FAQ and the API docs are in the Cygwin repo under
winsup/doc:
https://cygwin.com/git/gitweb.cgi?p=newlib-cygwin.git
Documentation tends to be a bit back in time (*nobody* wants to write
docs!!1!11) so we appreciate any help.
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-05-30 9:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-29 1:40 Oleksandr Gavenko
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 [this message]
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=20160530093749.GA6659@calimero.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).