From: "Gary R. Van Sickle" <g.r.vansickle@worldnet.att.net>
To: <cygwin@cygwin.com>
Subject: RE: YA in the "try a snapshot" series (was Re: latest cvs fork problems)
Date: Mon, 21 Oct 2002 23:23:00 -0000 [thread overview]
Message-ID: <NCBBIHCHBLCMLBLOBONKKEMPDGAA.g.r.vansickle@worldnet.att.net> (raw)
In-Reply-To: <20021022041028.GA27238@redhat.com>
> On Mon, Oct 21, 2002 at 10:42:45PM -0500, Gary R. Van Sickle wrote:
> >>I was able to duplicate Jason's mmap problem with his version of exim
> >>and, so, I think I was also able to fix it.
> >>
> >>The latest snapshot should solve this problem. The hanging problem
> >>that I mentioned previously seems to be gone, too... or, more likely,
> >>it will manifest itself 10 seconds after I send this email.
> >>
> >
> >Not sure if this would be expected to affect my perl problems, but it
> >hasn't made any difference. Cygcheck attached FWIW.
>
> I asked for some specific things wrt your perl problems. cygcheck was
> item 1 of 3.
>
> FWIW, I doubt that I'm going to be able to fix this problem at the rate
> of one response to information every five days.
I don't recall requesting that anybody fix this problem. And I apologize if my
rate of information flow regarding said problem is too slow; I have many
masters, and Cygwin too often has to wait.
> I'm not trying to be
> flip. This is just a realistic assessment of what is required to debug
> problems like this. I am 99% sure that rebasing will probably solve
> your particular problem, though.
We'll find out in 10 days I guess.
--
Gary R. Van Sickle
Brewer. Patriot.
--
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/
next prev parent reply other threads:[~2002-10-22 4:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-17 11:28 latest cvs fork problems Rob Napier
2002-10-17 11:41 ` Christopher Faylor
2002-10-18 6:38 ` Jason Tishler
2002-10-18 8:23 ` Christopher Faylor
2002-10-18 8:31 ` Jason Tishler
2002-10-18 18:29 ` Christopher Faylor
2002-10-18 18:59 ` Jason Tishler
2002-10-18 19:25 ` Christopher Faylor
2002-10-18 22:05 ` Christopher Faylor
2002-10-20 19:09 ` YA in the "try a snapshot" series (was Re: latest cvs fork problems) Christopher Faylor
2002-10-21 8:19 ` Jason Tishler
2002-10-21 12:30 ` Norman Vine
2002-10-21 13:55 ` Christopher Faylor
2002-10-21 15:20 ` Norman Vine
2002-10-21 20:42 ` Norman Vine
2002-10-22 18:41 ` Norman Vine
2002-10-22 19:13 ` snapshots R us Christopher Faylor
2002-10-22 21:57 ` Gary R. Van Sickle
2002-10-23 0:22 ` Christopher Faylor
2002-10-23 0:41 ` Gary R. Van Sickle
2002-10-21 21:46 ` YA in the "try a snapshot" series (was Re: latest cvs fork problems) Gary R. Van Sickle
2002-10-21 22:24 ` Christopher Faylor
2002-10-21 23:23 ` Gary R. Van Sickle [this message]
2002-10-22 4:14 ` Roman Belenov
2002-10-22 10:57 ` Jason Tishler
2002-10-18 17:41 ` latest cvs fork problems Jason Tishler
2002-10-21 20:28 YA in the "try a snapshot" series (was Re: latest cvs fork problems) Pierre A. Humblet
2002-10-21 20:33 ` 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=NCBBIHCHBLCMLBLOBONKKEMPDGAA.g.r.vansickle@worldnet.att.net \
--to=g.r.vansickle@worldnet.att.net \
--cc=cygwin@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).