From: Ben Elliston <bje@redhat.com>
To: <girke@itu304.ut.TU-Berlin.DE>
Cc: <sourcenav@sources.redhat.com>
Subject: Re: Problem under WinNT4 Server SP5
Date: Thu, 30 Nov 2000 15:57:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.30.0012011056130.26736-100000@moshpit.cygnus.com> (raw)
In-Reply-To: <Pine.A32.3.96.1001128102630.8134A-100000@itu304.ut.TU-Berlin.DE>
Do you have any idea?
Are you able to hone in on the problem code by partitioning your project
down until you've only got a few source files? When you do, can you post
them somewhere?
Ben
prev parent reply other threads:[~2000-11-30 15:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-30 7:19 girke
2000-11-30 15:57 ` Ben Elliston [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.30.0012011056130.26736-100000@moshpit.cygnus.com \
--to=bje@redhat.com \
--cc=girke@itu304.ut.TU-Berlin.DE \
--cc=sourcenav@sources.redhat.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).