Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Authentication-Warning: mdssirds.comp.pge.com: esp5 set sender to esp5 AT pge DOT com using -f Date: Mon, 13 Oct 2003 21:59:10 -0700 From: Edward Peschko To: cygwin AT cygwin DOT com Subject: Re: merging mingw and cygwin Message-ID: <20031014045910.GB28478@mdssirds.comp.pge.com> References: <20031012062347 DOT GA12677 AT mdssirds DOT comp DOT pge DOT com> <20031013190000 DOT GB20245 AT mdssirds DOT comp DOT pge DOT com> <20031013203527 DOT GA25036 AT mdssirds DOT comp DOT pge DOT com> <20031013213226 DOT GC25036 AT mdssirds DOT comp DOT pge DOT com> <20031013224522 DOT GB26012 AT mdssirds DOT comp DOT pge DOT com> <20031014021908 DOT GH22296 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031014021908.GH22296@redhat.com> User-Agent: Mutt/1.4.1i On Mon, Oct 13, 2003 at 10:19:08PM -0400, Christopher Faylor wrote: > Apparently you decided to bcc me on this email. > > IIRC, I asked not to receive personal email from you on this subject. I > suggested that you continue your discussion in the cygwin mailing list > and it should be obvious to anyone that I read the mailing list and was > reading this thread, in fact. So, there was no need to do this even > if I hadn't explicitly asked you to not send me personal mail. > > Do not send me personal email about cygwin again. I bcc'ed you about this because it was your decision about the email was in large part responsible for the somewhat antagonistic tone that developed in the thread on cygwin AT cygwin DOT com. Frankly the terseness of it (saying 'it will never happen' before even understanding what 'it' was), and the discourtesy expressed in your attitude pissed me off and it is not at all professional. And no, this email - *and the last email* - was not about cygwin, it was about conduct. You hold the keys to some sort of power, the power to enter the developer's list, the power to patch cygwin effectively. For you to issue a blanket statement that I am not to communicate to you about cygwin and hence never to enter that list is a disabuse of power. The BCC was a courtesy to you, just to remind you who said the 'blanket no' and perhaps to allow you to re-think your position. And FYI - I agreed with Larry Hall. cygwin-patches is probably the better mailing list for me; it fits more with what I want to do. If you had pointed me in that direction (after a couple of friendly questions on my part rather than an all-out blanket statement saying 'it will never happen') a flame war could have been averted. And even though this is in its essence, a personal letter, I will obey the letter of your law, and post it publicly. In a way, its probably better this way. Power issues are a matter of public import, and this is a hell of a power issue. Ed -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/