public inbox for cygwin-cvs@sourceware.org help / color / mirror / Atom feed
From: Corinna Vinschen <corinna@sourceware.org> To: cygwin-cvs@sourceware.org Subject: [newlib-cygwin] Cygwin: FAQ 1.6: Update "Who's behind the project?" Date: Mon, 13 Jul 2020 15:20:19 +0000 (GMT) [thread overview] Message-ID: <20200713152019.119EC3851C12@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=b1237e64fd03a3b802b9fedde298505e22b3f07f commit b1237e64fd03a3b802b9fedde298505e22b3f07f Author: Brian Inglis <Brian.Inglis@SystematicSW.ab.ca> Date: Mon Jul 13 07:30:07 2020 -0600 Cygwin: FAQ 1.6: Update "Who's behind the project?" winsup/doc/faq-what.xml: remove Red Hat, Net, Win32 references and clean up Diff: --- winsup/doc/faq-what.xml | 33 ++++++++++++++++----------------- 1 file changed, 16 insertions(+), 17 deletions(-) diff --git a/winsup/doc/faq-what.xml b/winsup/doc/faq-what.xml index 772fc0464..ea8496ccb 100644 --- a/winsup/doc/faq-what.xml +++ b/winsup/doc/faq-what.xml @@ -124,29 +124,28 @@ questions, all of these people will appreciate it if you use the cygwin mailing lists rather than sending personal email.)</emphasis> </para> <para> -Corinna Vinschen is the current project lead. Corinna is a senior Red Hat -engineer. Corinna is responsible for the Cygwin library and maintains a couple -of packages, for instance OpenSSH, OpenSSL, and a lot more. +Corinna Vinschen is the current project lead, +responsible for the Cygwin library and a lot more. </para> <para> -Yaakov Selkowitz is another Red Hat engineer working on the Cygwin project. -He's the guy behind the current build and packaging system and maintains by -far the most packages in the Cygwin distribution. +Yaakov Selkowitz is the guy behind the current build and packaging system +and maintained by far the most packages in the Cygwin distribution. </para> <para> -Jon Turney is developer and maintainer of the Cygwin X server and a couple -of related packages. +Jon Turney is maintainer of the Cygwin X server and related packages. </para> <para> -The packages in the Net release are maintained by a large group of people; -a complete list can be found -<ulink url='https://cygwin.com/cygwin-pkg-maint'>here</ulink>. -</para> -<para>Please note that all of us working on Cygwin try to be as responsive as -possible and deal with patches and questions as we get them, but realistically -we don't have time to answer all of the email that is sent to the main mailing -list. Making Net releases of the Win32 tools and helping people on the Net out -is not our primary job function, so some email will have to go unanswered. +The packages are maintained by a large group of +<ulink url='https://cygwin.com/cygwin-pkg-maint'>volunteers</ulink>. +</para> +<para> +Please note that all of us volunteering on Cygwin try to be as responsive as +possible and deal with patches and questions as we get them, but +realistically we don't have time to answer all of the email that is sent to +the main mailing list. +Making releases of the tools and packages is an activity in our spare time, +helping people out is not our primary focus, so some email will have to go +unanswered. </para> <para>Many thanks to everyone using the tools for their many contributions in the form of advice, bug reports, and code fixes. Keep them coming!
reply other threads:[~2020-07-13 15:20 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200713152019.119EC3851C12@sourceware.org \ --to=corinna@sourceware.org \ --cc=cygwin-cvs@sourceware.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: linkBe 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).