From: Niels Skou Olsen <nso@manbw.dk>
To: sourcenav@sources.redhat.com
Subject: Re: AW: S-N 4.5.2 hangs while scanning header file
Date: Fri, 24 Nov 2000 01:03:00 -0000 [thread overview]
Message-ID: <u7l5tg2uo.fsf@manbw.dk> (raw)
In-Reply-To: <Pine.LNX.4.30.0011240706350.1232-100000@moshpit.cygnus.com>
bje@redhat.com writes:
> That's a good thing. Now, the problem is, how are you going to contribute
> the file? It is no doubt under Borland copyright.
One way to narrow it down is to do a "binary search": Cut the file in half
an check each half. Then continue this process recursively on the failing
halves until you have a small enough chunk of header file that fails. If
everything goes well, you'll end up with a small enough chunk that you can
"rewrite" it. This will not violate any copyrights..
Best regards
--
Niels Skou Olsen, M.Sc.
Intelligent Engine, R&D
MAN B&W Diesel A/S
next prev parent reply other threads:[~2000-11-24 1:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-23 8:56 Fischer Martin (AT/EES3)
2000-11-23 12:07 ` Ben Elliston
2000-11-24 1:03 ` Niels Skou Olsen [this message]
[not found] <01CDE14BF507D2119A0C00805FBBB713016322B8@ermail3.er.bosch.de>
2000-11-24 15:59 ` Ben Elliston
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=u7l5tg2uo.fsf@manbw.dk \
--to=nso@manbw.dk \
--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).