From: Michael Chastain <mec.gnu@mindspring.com>
To: manjo@austin.ibm.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/testsuite] gdb_file_cmd: enhance return value
Date: Mon, 30 Aug 2004 20:59:00 -0000 [thread overview]
Message-ID: <4133953A.nailGLM1C8JMN@mindspring.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0408301435220.7599@lazy>
> Have you commited these changes to the testcase already? I just checked
> out cvs -z9 -d :ext:manjo@sources.redhat.com:/cvs/src co src/gdb and I did
> not see changes to the testcases. Am I checking out the correct tree??
You've got the right tree.
I changed the callers only enough to work with the new return
value of { "" } on success. I didn't do the { "" nodebug } part
in the callers.
I could have done that part too -- it would be less checkins to gdb
overall and less work for you. But it felt kind of funny just taking
over like that. So I didn't glom that part; I left that for you to do,
to help bring up your skills more, build the gdb team, that kinda stuff.
Michael
prev parent reply other threads:[~2004-08-30 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 23:40 Michael Chastain
2004-08-28 23:59 ` Michael Chastain
2004-08-30 20:12 ` Manoj Iyer
2004-08-30 20:59 ` Michael Chastain [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=4133953A.nailGLM1C8JMN@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=gdb-patches@sources.redhat.com \
--cc=manjo@austin.ibm.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