From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: delete_breakpoint: don't try to insert other breakpoints
Date: Fri, 16 Nov 2007 11:15:00 -0000 [thread overview]
Message-ID: <uodducuj4.fsf@gnu.org> (raw)
In-Reply-To: <200711161334.40641.vladimir@codesourcery.com> (message from Vladimir Prus on Fri, 16 Nov 2007 13:34:40 +0300)
> From: Vladimir Prus <vladimir@codesourcery.com>
> Date: Fri, 16 Nov 2007 13:34:40 +0300
> Cc: gdb-patches@sources.redhat.com
>
> > I'm okay with making the code cleaner, but on at a price of removing
> > features, even if they are currently unused.
>
> Let me clarify
No need, I understood you the first time.
> Why keep unused code in HEAD?
I'm sorry, I already said why I'm opposed to it. I have nothing
further to add to what I said.
next prev parent reply other threads:[~2007-11-16 11:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 20:24 Vladimir Prus
2007-11-15 4:04 ` Eli Zaretskii
2007-11-15 5:59 ` Vladimir Prus
2007-11-16 10:13 ` Eli Zaretskii
2007-11-16 10:34 ` Vladimir Prus
2007-11-16 11:15 ` Eli Zaretskii [this message]
2007-11-16 13:02 ` Daniel Jacobowitz
2007-11-16 14:14 ` Vladimir Prus
2007-11-16 15:09 ` Eli Zaretskii
2007-11-16 21:44 ` Nick Roberts
2007-11-16 22:24 ` Vladimir Prus
2007-11-17 9:13 ` Eli Zaretskii
2007-11-18 1:25 ` Nick Roberts
2007-12-16 21:13 ` Daniel Jacobowitz
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=uodducuj4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@codesourcery.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