From: Daniel Jacobowitz <drow@false.org>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] gdb-freeplay
Date: Thu, 11 Sep 2008 23:22:00 -0000 [thread overview]
Message-ID: <20080911232120.GA25741@caradoc.them.org> (raw)
In-Reply-To: <48C99BE5.3020500@vmware.com>
On Thu, Sep 11, 2008 at 03:29:57PM -0700, Michael Snyder wrote:
> > It doesn't look
>> like it, in which case it's probably more sensible to put it in a
>> separate directory.
>
> Maybe -- but gdbreplay doesn't share any code with
> gdbserver either.
IMO, historical accident; gdbserver was smaller then :-)
>> As for actually committing it, I'd request that you fix the FIXMEs
>> first :-) I always hate committing code with that hanging around.
>
> I use fixme and to-do somewhat interchangeably.
> They're not really indicative of a bug or breakage.
>
> I could globally replace them with TO-DO if it makes you feel better.
> ;-)
Not really. It's just that checked in FIXMEs rarely get fixed.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2008-09-11 23:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 0:23 Michael Snyder
2008-09-11 20:17 ` Daniel Jacobowitz
2008-09-11 22:31 ` Michael Snyder
2008-09-11 23:22 ` Daniel Jacobowitz [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=20080911232120.GA25741@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