X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.9 required=5.0	tests=AWL,BAYES_00,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
X-IronPortListener: Outbound_SMTP
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAJxONE+cKEdK/2dsb2JhbABDr1yBB4FyAQEBBBIoPxIBCA0LHAIvEyYBBA4NGqRzm3aLMQMoCQkMCQYLDwoELYMNBkuDO2MEiEiERI4fhRaHbg
From: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder AT niaid DOT nih DOT gov>
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
CC: "'Matt Seitz (matseitz)'" <matseitz AT cisco DOT com>
Date: Thu, 9 Feb 2012 17:58:16 -0500
Subject: RE: Cygwin.dll version in bug reports
Message-ID: <0105D5C1E0353146B1B222348B0411A20A51C567D1@NIHMLBX02.nih.gov>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id q19Mwbpn029348

Matt Seitz (matseitz) sent the following at Thursday, February 09, 2012 3:04 PM
>> On Wed, Feb 08, 2012 at 05:17:18PM -0800, Matt Seitz (matseitz) wrote:
>> >
>> >Today I sent a couple of bug reports.  I based my "Subject" on the
>> >examples" given at:
>> >
>> >http://cygwin.com/problems.html
>> >
>> >Since all the good examples had a cygwin1.dll version at the front, I
>> >thought that was expected.  So I put 1.7.10 at the front, because
>> >was the cygwin1.dll version I was using.
>>
>> The "good examples" mentioned in the problems.html page refer to
>> problems reported for the Cygwin DLL.
>
>OK, then I misunderstood the examples.
>
>Perhaps it would help to include some examples that cite the package
>version instead of the DLL version?

I wouldn't presume to speak for the package maintainers.  However, I
would guess that people assume that the package version is the latest.
(I do.)  So if one is up to date, why the need to point it out in the
subject line?

But it is good to make a statement in the body of the email that
"Everything is up to date", just to eliminate that variable/question.
And if everything isn't, explain why not and expect to be asked to
update your installation to the latest.

Good luck,

- Barry
  Disclaimer: Statements made herein are not made on behalf of NIAID.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple