From: Christopher Faylor <cygwin@cygwin.com>
To: "Jesse S. Miller" <jsmille@LearnLink.Emory.Edu>
Cc: cygwin@cygwin.com
Subject: Re: [PATCH] turn on timercmp, et al, for cygwin
Date: Sun, 11 Nov 2001 08:26:00 -0000 [thread overview]
Message-ID: <20011116013907.GD13107@redhat.com> (raw)
In-Reply-To: <fc.00249f0f0fa3918800249f0f0fa39188.fa398eb@LearnLink.Emory.Edu>
Please check out the project web page for links to available information
and ports: http://cygwin.com/ .
If you don't see what you need there, then the cygwin mailing list is
the best place to make observations or get questions answered.
Information on the mailing list is available at the project web page.
For your convenience, I've reset the Reply-To: address to point to the
cygwin mailing list. I've also Cc'ed this reply there.
On Thu, Nov 15, 2001 at 08:18:55PM -0500, Jesse S. Miller wrote:
>Dear Christopher
> I apologize for the inconvenience, but I found a post you made to a
>Redhat forum regarding time.h in Cygwin.
>
>The page where I found your post was
>http://sources.redhat.com/ml/newlib/2001/msg00248.html
>
>Will this patch enable the proper functionality of all (or most) of the
>time.h functions? If so, could you assist me in applying this patch to my
>version of Cygwin? I'm not terribly knowledeable in Unix, so I'm a bit
>confused as to how to actually apply the the changes.
>
>(I know nothing about CVS or diff, etc, but I need to emulate the Unix
>environment for a program I'm running and the time.h functions are
>important to that program.)
>
>I'd appreciate any help you could give me.
>
>
>
>
>Jesse Miller
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
parent reply other threads:[~2001-11-16 1:39 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <fc.00249f0f0fa3918800249f0f0fa39188.fa398eb@LearnLink.Emory.Edu>]
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=20011116013907.GD13107@redhat.com \
--to=cygwin@cygwin.com \
--cc=jsmille@LearnLink.Emory.Edu \
/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).