Mail Archives: cygwin/2002/06/26/11:13:50
Chris,
Perhaps it might be suitable to create a cygwin-bug mailing list so that
we can isolate actual bug reports from general discussion, newbie
questions, requests, etc. Seeing as how the project has grown and the
fact that other large projects on sources seem to have this type of
setup, it seems like the logical course of action. It think that it
would definately cut back on the amount of volume on the main list, but
I could be wrong. Furthermore, if we were to establish a profile on the
redhat bugzilla, I believe that bug-reporting could be streamlined and
potentially provide more details. At the very least, it would mean less
things for people to remeber to do. I'm going to go out on a limb here
and say I believe more people are using Cygwin then in the past. So if
this was discussed in the past, I think it might be worth revisiting
this now. Anyhow, I just thought I get yours and other's take on this
suggestion.
Cheers,
Nicholas
Christopher Faylor wrote:
>On Tue, Jun 25, 2002 at 10:59:59PM -0400, Pierre A. Humblet wrote:
>
>>I don't know if this is the best venue to point to potential
>>issues with the cvs build, but here it is.
>>
>
>The definitive answer for what the mailing lists are used for is:
>
>http://cygwin.com/lists.html .
>
>The description of cygwin-patches is this:
>
>cygwin-patches: a list for submitting patches to the Cygwin DLL and the
>other components of the "winsup" directory (if you aren't sure what this
>means, then you shouldn't be sending email here). Discussions of
>supplied patches are also acceptable, of course. Only subscribers may
>submit email to this list.
>
>Since your email did not include a patch or discussion of a patch, I
>guess you can draw your own conclusion.
>
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -