From: mwoehlke <mwoehlke@tibco.com>
To: cygwin-talk@cygwin.com
Subject: Re: Um... what format are Cygwin manpages?
Date: Thu, 10 Aug 2006 20:45:00 -0000 [thread overview]
Message-ID: <ebg5l8$5f2$2@sea.gmane.org> (raw)
In-Reply-To: <20060810202721.GC935@trixie.casa.cgf.cx>
Christopher Faylor wrote:
> On Thu, Aug 10, 2006 at 03:20:21PM -0500, mwoehlke wrote:
>> Anyway, if it turns out I have to patch an info file, then I guess I'm
>> stuck doing that. Assuming anyone on newlib pays attention to me. So
>> far, zilch.
>
> Yes, you definitely have to *patch* the *source* of the documentation that
> you want changed if you want someone to apply it.
I think the point is that I would hope they would accept a flat-out new
file, if it was that major a re-working (which IMO it should be; I find
the layout of glibc's manpage a lot easier to understand, in addition to
being more accurate).
But... if I'm to do anything with the texinfo source, I have to *find*
it first. Sigh. I am losing enthusiasm for this project.
--
Matthew
vIMprove your life! Now on version 7!
next parent reply other threads:[~2006-08-10 20:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ebd0om$gjh$1@sea.gmane.org>
[not found] ` <cb51e2e0608092159t14175e52jeb656ffd2cc123a1@mail.gmail.com>
[not found] ` <ebfiu4$4pn$1@sea.gmane.org>
[not found] ` <cb51e2e0608101108g41c88386wd7219aaead8ca396@mail.gmail.com>
[not found] ` <ebg4e5$39g$1@sea.gmane.org>
[not found] ` <20060810202721.GC935@trixie.casa.cgf.cx>
2006-08-10 20:45 ` mwoehlke [this message]
2006-08-10 20:54 ` Christopher Faylor
2006-08-10 21:21 ` mwoehlke
2006-08-10 21:31 ` Christopher Faylor
2006-08-10 22:26 ` What's wrong with *roff, anyway? (Was: Um... what format are Cygwin manpages?) mwoehlke
2006-08-11 8:34 ` Corinna Vinschen
2006-08-11 15:30 ` mwoehlke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ebg5l8$5f2$2@sea.gmane.org' \
--to=mwoehlke@tibco.com \
--cc=cygwin-talk@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).