From: Daniel Jacobowitz <drow@false.org>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] Resubmit, reverse debugging [0/5]
Date: Sat, 11 Oct 2008 02:43:00 -0000 [thread overview]
Message-ID: <20081010185808.GA12193@caradoc.them.org> (raw)
In-Reply-To: <48EFA065.5070108@vmware.com>
On Fri, Oct 10, 2008 at 11:35:17AM -0700, Michael Snyder wrote:
> OK, I agree -- but it's in use, in the field.
>
> Wouldn't the practice be to deprecate it, and announce
> the intention of removing it at some future time, rather
> than just suddenly take it away?
Sorry, but it's hard to be sympathetic to this. I go through this on
a regular basis, so do other GDB contributors: it's the risk you take
for deploying things before they're merged. If you don't get at least
the protocol documentation committed to the master repository, then
this is what happens.
Speaking of documentation, is there a documentation part for the
remote protocol changes? I haven't seen one in the most recent patch
set, and I don't want any new protocol extensions without docs (for
the obvious reason).
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-10-11 2:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 2:17 Michael Snyder
2008-10-10 17:44 ` Michael Snyder
2008-10-10 17:54 ` Daniel Jacobowitz
2008-10-10 18:38 ` Michael Snyder
2008-10-11 2:43 ` Daniel Jacobowitz [this message]
2008-10-11 2:48 ` Michael Snyder
2008-10-11 8:02 ` Eli Zaretskii
2008-10-13 19:21 ` Michael Snyder
2008-10-14 7:56 ` Jakob Engblom
2008-10-14 9:07 ` teawater
2008-10-14 12:24 ` Daniel Jacobowitz
2008-10-14 12:27 ` Daniel Jacobowitz
2008-10-15 18:20 ` Michael Snyder
2008-10-15 18:30 ` Daniel Jacobowitz
2008-10-15 18:42 ` Michael Snyder
2008-10-15 18:47 ` Pedro Alves
2008-10-15 18:49 ` Michael Snyder
2008-10-11 9:47 ` Joel Brobecker
2008-10-13 19:22 ` Michael Snyder
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=20081010185808.GA12193@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.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