This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: [ANNOUNCEMENT] Updated: apr(-util) 0.9.7-1
On Tue, Nov 15, 2005 at 04:02:45PM -0800, Yitzchak Scott-Thoennes wrote:
>On Tue, Nov 15, 2005 at 03:51:10PM -0500, Christopher Faylor wrote:
>> On Tue, Nov 15, 2005 at 07:37:53PM +0000, zzapper wrote:
>> >On Mon, 14 Nov 2005 21:01:43 +0000, wrote:
>> >>zzapper wrote:
>> >>> On Sun, 13 Nov 2005 16:16:58 +0000, wrote:
>> >>>>APR and APR-util, portability and miscellaneous utility libraries,
>> >>>>have been updated in the Cygwin net distribution to version 0.9.7-1.
>> >>>
>> >>> Gosh this was hard to Google
>> >>>
>> >>> I think it's
>> >>>
>> >>> sdesc: "Additional utility library for use with the Apache Portable Runtime
>> >>> (development/documentation package)"
>> >>> ldesc: "The mission of the Apache Portable Runtime (APR) project is to create
>> >>> and maintain software libraries that provide a predictable and consistent
>> >>> interface to underlying platform-specific implementations.
>> >>
>> >>
>> >>I have no idea what you are trying to say, zzapper.
>> >
>> >I was just trying to find some doc on APR, as I didn't even know what it was.
>>
>> Please don't bother the mailing list with your lack of knowledge about
>> things like this.
>
>To clarify:
>
>zzapper has often responded to announcements that don't describe the
>package with a short description s/he has found by searching.
often == very sporadically.
>Are you asking that s/he no longer do this? Or not do it when the only
>description s/he finds is from the setup hint? Or other?
Do you think it makes any sense to send ambiguous observations to the
mailing list which confuse the package maintainer (and me for that
matter)? Is it really important that we know that "I didn't even know
what it was"?
If zzapper can't respond to an announcement in such a way that the intent
is clear, then I would prefer that no responses should be sent at all.
cgf
--
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/