From: "Eli Zaretskii" <eliz@gnu.org>
To: gdb-patches@sources.redhat.com
Subject: Re: RFC: Gdbserver unit testing
Date: Mon, 11 Apr 2005 20:18:00 -0000 [thread overview]
Message-ID: <01c53ed3$Blat.v2.4$2c91c760@zahav.net.il> (raw)
In-Reply-To: <20050411141313.GA11140@nevyn.them.org> (message from Daniel Jacobowitz on Mon, 11 Apr 2005 10:13:13 -0400)
> Date: Mon, 11 Apr 2005 10:13:13 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: gdb-patches@sources.redhat.com
>
> > Yes. But please consider renaming the directory to gdb.server
> > instead, as that would save us from the misery of having to add an
> > entry for every file there.
>
> Thanks. That seems like a good idea... done as attached.
Thank you.
prev parent reply other threads:[~2005-04-11 20:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-27 3:00 Daniel Jacobowitz
2005-04-08 12:58 ` Daniel Jacobowitz
2005-04-09 8:14 ` Eli Zaretskii
2005-04-11 14:13 ` Daniel Jacobowitz
2005-04-11 20:18 ` Eli Zaretskii [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='01c53ed3$Blat.v2.4$2c91c760@zahav.net.il' \
--to=eliz@gnu.org \
--cc=gdb-patches@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