From: Tom Tromey <tromey@redhat.com>
To: Fernando Nasser <fnasser@redhat.com>
Cc: Insight List <insight@sourceware.cygnus.com>
Subject: Re: Patch: saving breakpoints
Date: Tue, 15 May 2001 13:32:00 -0000 [thread overview]
Message-ID: <87ofsu730r.fsf@creche.redhat.com> (raw)
In-Reply-To: <3B018568.6FD7C2C5@redhat.com>
>>>>> "Fernando" == Fernando Nasser <fnasser@redhat.com> writes:
Fernando> If: 1) The experience shows us that may be a better way
Fernando> AND
Fernando> 2) Someone does find the time to implement another algorithm
Fernando> then we can always change or improve the heuristic in the
Fernando> future. But it is time to move ahead and add some new
Fernando> features.
As a general approach I strongly agree with this. It is very
scientific, and we've seen before how improvements come from using the
existing code for a while and then seeing how it could be better.
Fernando> P.S.: Last time I asked Tom to postpone it because we had
Fernando> some other priorities and the code he needed to change was
Fernando> undergoing some changes. It was just bad timing.
Yeah. This patch is actually based on the old one but is more
complete.
Tom
prev parent reply other threads:[~2001-05-15 13:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-11 18:47 Tom Tromey
2001-05-15 12:39 ` Fernando Nasser
2001-05-15 13:32 ` Tom Tromey [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=87ofsu730r.fsf@creche.redhat.com \
--to=tromey@redhat.com \
--cc=fnasser@redhat.com \
--cc=insight@sourceware.cygnus.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).