From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-talk@cygwin.com
Subject: Re: patch to add C99 complex
Date: Fri, 08 Oct 2010 15:45:00 -0000 [thread overview]
Message-ID: <20101008154504.GD23848@ednor.casa.cgf.cx> (raw)
In-Reply-To: <163573.23386.qm@web25507.mail.ukl.yahoo.com>
On Fri, Oct 08, 2010 at 04:22:19PM +0100, Marco Atzeri wrote:
>Next week I should add the documentation to complete the work.
Documentation? Don't you mean you're going to set up your own web site
devoted to complex functions in Cygwin? I think we all know that's the
most effective way disseminate information about Cygwin. Keeping the
information distributed means there is no single point of documentation
failure.
cgf
next parent reply other threads:[~2010-10-08 15:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101008151733.GA23848@ednor.casa.cgf.cx>
[not found] ` <163573.23386.qm@web25507.mail.ukl.yahoo.com>
2010-10-08 15:45 ` Christopher Faylor [this message]
2010-10-08 15:49 ` Eric Blake
2010-10-08 15:58 ` Christopher Faylor
2010-10-09 2:06 ` Dave Korn
2010-10-08 16:04 ` Marco Atzeri
2010-10-08 16:08 ` Christopher Faylor
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=20101008154504.GD23848@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.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).