Get that Linux feeling - on Windows
Is there a mailing list for the project?
Yes. There are several. They are listed below.
That depends. Have you researched your question already? Cygwin is not a new project. It has been around for many years. That means that almost any question has probably already been asked. Places to check for information would be the Cygwin FAQ, the Cygwin documentation, the web, and the mailing list archives (click on a mailing list name below to search the archive).
Now that you searched the information sources and came up blank, let us say that there are a lot of friendly folk who will probably try to answer your questions. However, if you are going to ask a question, you should make sure that you ask in a way which allows the folks on the list to answer your question most easily. Vague, content-free, or repetitive queries or observations are not overly likely to get an answer.
- None of the below lists accept html mail. Use plain text only.
- Please read the general mailing list FAQ for sourceware.org (the host of this site).
- Please do not feed the spammers by including raw email addresses in the body of your message.
- All of the messages you send to these mailing lists will be archived. If you include sensitive information in your message it will be viewable by anyone. That includes email addresses, phone numbers, addresses, etc. Site policy is to not edit the archives except, possibly, to remove viruses. This means that your information will be viewable by posterity, so be careful.
In general, you should send questions and bug reports here. This is
the list for discussion of just about all things
related to the Cygwin community release. If you have questions about how to
use Cygwin, or if you have Cygwin-specific
(see above) questions,
problems, or observations about the UNIX tools
(bash, gcc, make, etc.) that come with Cygwin, this is the list for you
(although it's very possible that you will receive more qualified help for
such tools on their specific non-Cygwin mailing lists). There are
a few exceptions to the "all things Cygwin" nature of this list:
- Patches for the Cygwin DLL should go to the cygwin-patches mailing list (see below).
- New package submissions should go to the cygwin-apps mailing list (see below).
- Questions about Cygwin licensing, copyright, and GPL issues should go to the moderated cygwin-licensing list (see below).
- Questions about other Cygwin releases not downloaded from
the Cygwin website or its mirrors are
strongly discouraged. In theory, there should be better forums for
discussing this kind of unsponsored software than the Cygwin mailing list.
This caveat applies to all of the mailing lists at this site.
- cygwin-announce: a moderated announcement list solely for announcements related to the official Cygwin release. Announcements sent to cygwin-anounce are automatically sent to the Cygwin mailing list so there is no reason to subscribe to both mailing lists if your only intent is to be up-to-date on new package releases.
- cygwin-apps: a subscriber-only list for package maintainers to discuss packaging issues regarding applications that are distributed with the Cygwin DLL. Do not subscribe if you are not interested in being a package maintainer. If you are maintaining or volunteering to maintain one of the packages that is distributed with the Cygwin net releases you should be subscribed to this list. This list is intended for discussing solutions. It is not for bug reports, "it would be nice", or "how do I" type of musings. Do not subscribe to this mailing list to ask questions about packages. Use the main Cygwin mailing list for that.
a subscribers-only list for discussing the internals of the Cygwin DLL
and all cygwin components of the "winsup" directory. Discussion of upcoming
net releases is also appropriate. Please do not subscribe or send email to
this list if you do not understand what is meant by "the winsup directory".
If you are interested in contributing to the development of Cygwin, this is the place to discuss your plans. If you have an issue and hope that someone will look into it for you then please do not send email here. This is a mailing list for doers not musers.
- cygwin-patches: a list for submitting patches to the Cygwin DLL and the other components of the "winsup" directory. Discussions of supplied patches are also acceptable, of course. Only subscribers may submit email to this list.
- cygwin-cvs: a read-only list which receives log messages for every GIT commit in the 'winsup' directory. If you don't know what this means then you probably shouldn't subscribe. Messages consist of a log message and pointers to diffs of the changes.
- cygwin-apps-cvs: a list which receives log messages for every GIT and CVS commit in the 'cygwin-apps' repository. If you don't know what this means then you probably shouldn't subscribe. Messages consist of a log message and pointers to diffs of the changes.
- cygwin-talk: a chatter list for discussing things that are tangentially related to Cygwin. This list is intended to be funny but not terribly helpful. Do not send technical questions about Cygwin here. Responses to technical questions in this list are not guaranteed to be serious or definitive, probably the opposite. No profanity, no commercial posts, and minimal flaming, please.
Clicking on any of the above mailing list links will take you to the mailing list archives.
Mail sent to firstname.lastname@example.org will go to the list.
Subscribing and unsubscribing
You can subscribe to or unsubscribe from any of the above lists by sending a blank (no subject, no body) email to email@example.com or firstname.lastname@example.org respectively.
Or, you can use the form below to subscribe to or unsubscribe from all of the lists.
If you have any questions or problems with the mailing lists, see the Sourceware mailing list FAQs.
Before you send any mail to one of these lists, you need to read the relevant Cygwin documentation, especially the Cygwin FAQ, and the mailing list archives so that you don't ask a question that someone has already asked or report a bug that has already been reported.