X-Spam-Check-By: sourceware.org Message-ID: <44DA6171.2000503@cygwin.com> Date: Wed, 09 Aug 2006 18:28:01 -0400 From: "Larry Hall (Cygwin)" Reply-To: cygwin AT cygwin DOT com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20060112 Fedora/1.5-1.fc4.remi Thunderbird/1.5 Mnenhy/0.7.4.0 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Um... what format are Cygwin manpages? References: <20060809182417 DOT GB29752 AT trixie DOT casa DOT cgf DOT cx> <44DA414F DOT 8070802 AT cygwin DOT com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 mwoehlke wrote: > Larry Hall (Cygwin) wrote: >> mwoehlke wrote: >>> Christopher Faylor wrote: >>>> On Wed, Aug 09, 2006 at 01:10:11PM -0500, mwoehlke wrote: >>>>> I have a modified Linux manpage almost ready to go; I assume that >>>>> goes to cygwin.patches? >>>> >>>> No, that would be appropriate only if the man page was found in the >>>> winsup hierarchy. The first line of printf(3) says "NEWLIB" when >>>> I type "man 3 printf" so that's where a man page patch should go. >>> >>> Ok, that's what I kind-of thought... Hmm, shame on the newlib folks >>> for having such a poorly-up-to-date manpage. :-) Anyway, I guess this >>> means that gmane.comp.lib.newlib will suffice? >> >> If that equates to newlib at sources dot redhat dot com, then yes. > > http://gmane.org/list-address.php?group=gmane.comp.lib.newlib > Seems to... > >>> (But... this means what? If the newlib folks don't like it, Cygwin is >>> just stuck with a /wrong/ manpage?) >> >> Well, we could scold them mercilessly and send them to their rooms >> without >> dinner. ;-) >> >> Let's not look for a problem that doesn't currently exist. > > Well then, let's hope they accept it. And in a timely manner, would be > nice. :-) > > Ok, so the other question... assuming it is accepted upstream tomorrow, > how long would it likely take to find its way into a Cygwin package? > You'd see it as soon as the maintainer of the cygwin-doc package released an update. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 -- 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/