From: Keith Seitz <keiths@redhat.com>
To: Ian Roxborough <irox@sbcglobal.net>
Cc: insight@sources.redhat.com
Subject: Re: Speaking of MS-Windows problems...
Date: Mon, 16 Dec 2002 10:04:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0212161003150.1489-100000@valrhona.uglyboxes.com> (raw)
In-Reply-To: <20021215113009.1a9ab33c.irox@sbcglobal.net>
On Sun, 15 Dec 2002, Ian Roxborough wrote:
> A while I ago I posted a patch that should help Insight stop
> crashing so much on MS-Windows platforms. Details here:
I remember this patch, but I am hesitant to use it, because it could be
covering up a more serious problem.
Well, I think it is time to admit that maybe that more serious problem
may be easier to track or solve than the current one.
What do others think? Should I check this in?
Keith
prev parent reply other threads:[~2002-12-16 18:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-15 11:39 Ian Roxborough
2002-12-16 10:04 ` Keith Seitz [this message]
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=Pine.LNX.4.44.0212161003150.1489-100000@valrhona.uglyboxes.com \
--to=keiths@redhat.com \
--cc=insight@sources.redhat.com \
--cc=irox@sbcglobal.net \
/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).