From: Yao Qi <yao@codesourcery.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 0/3] Keep track of files copied to host and target
Date: Fri, 22 Aug 2014 06:14:00 -0000 [thread overview]
Message-ID: <8761hlt5ph.fsf@codesourcery.com> (raw)
In-Reply-To: <21494.11553.21635.800922@ruffy2.mtv.corp.google.com> (Doug Evans's message of "Thu, 21 Aug 2014 10:32:17 -0700")
Doug Evans <dje@google.com> writes:
> Yao Qi writes:
> >
> > gdb/testsuite:
> >
> > 2014-08-21 Yao Qi <yao@codesourcery.com>
> >
> > * gdb.python/py-finish-breakpoint.exp: Copy .py file to host.
> > * gdb.python/py-finish-breakpoint2.exp: Likewise.
> > * gdb.python/python.exp: Likewise. Use .py file on the host
> > instead of the build.
>
> LGTM
>
OK, patch is pushed in.
> For reference sake,
>
> It seems there's a roughly equal measure of usage of
> remote_download versus gdb_remote_download in the testsuite
> for downloading to the host
> (though I didn't count which usages of gdb_remote_download
> actually need its extra functionality).
> Long term, if you wanted to migrate other uses of remote_download
> to gdb_remote_download for nothing other than consistency's sake
> that would be fine with me.
Thanks for letting us know your thoughts on this.
--
Yao (齐尧)
prev parent reply other threads:[~2014-08-22 6:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 4:04 Yao Qi
2014-08-15 4:04 ` [PATCH 3/3] Copy .py files to remote host Yao Qi
2014-08-15 4:04 ` [PATCH 1/3] Extend cleanfiles for multiple hosts Yao Qi
2014-08-15 4:04 ` [PATCH 2/3] Keep track of downloaded file in gdb_remote_download Yao Qi
2014-08-15 5:00 ` [PATCH 0/3] Keep track of files copied to host and target Doug Evans
2014-08-15 6:08 ` Yao Qi
2014-08-16 0:38 ` Doug Evans
2014-08-20 6:54 ` Yao Qi
2014-08-20 15:17 ` Pedro Alves
2014-08-20 15:48 ` Doug Evans
2014-08-21 0:35 ` Yao Qi
2014-08-21 17:32 ` Doug Evans
2014-08-22 6:14 ` Yao Qi [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=8761hlt5ph.fsf@codesourcery.com \
--to=yao@codesourcery.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
/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