Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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: Wed, 20 Aug 2014 06:54:00 -0000	[thread overview]
Message-ID: <53F4452E.9070902@codesourcery.com> (raw)
In-Reply-To: <CADPb22QwavUozC2w6KcjP0cr7LQBx7Z=P_ZtVzjdkbBS8Q+mkw@mail.gmail.com>

On 08/16/2014 08:38 AM, Doug Evans wrote:
> We could instead have a convention that we just don't bother to clean
> up files downloaded to remote hosts.

This patch https://sourceware.org/ml/gdb-patches/2009-11/msg00264.html
is the first one downloading files to remote host and deleting them when
test is finished.  After that, people just follow this convention, and
add test cases in this way.  Unfortunately, no technical reason is
mentioned in the patch about why we have to delete files on remote host.


> Sure, but I'd like to get a better understanding of the technical
> reasons for doing so.

I don't know any technical reasons either.  What I can tell from the
patch above is that "the first person did so, and the rest follow the
way he did".

Looks this patch set review is stalled.  You worried about the direction
or convention that we only delete part of files copied to host, but I
don't know the answer of your questions, which are about the convention
rather than patches.  I don't think my patch set makes it worse or
better.  It still make the effect of running testsuite unchanged, in
terms of files left on target and host.

At the same time, fails in gdb.python on remote host are still there
because patch 3/3 is pending.  My goal of this patch series is to fix
these fails, but I don't know how to move forward now.

-- 
Yao (齐尧)


  reply	other threads:[~2014-08-20  6:54 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 2/3] Keep track of downloaded file in gdb_remote_download Yao Qi
2014-08-15  4:04 ` [PATCH 1/3] Extend cleanfiles for multiple hosts Yao Qi
2014-08-15  4:04 ` [PATCH 3/3] Copy .py files to remote host 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 [this message]
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

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=53F4452E.9070902@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