This is the mail archive of the
mailing list for the Cygwin project.
RE: Cygwin.dll version in bug reports
- 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
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:
>> >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
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.
Disclaimer: Statements made herein are not made on behalf of NIAID.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple