public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: Re: [PATCH 1/1] [gdb/contrib] Add make-check-all.sh
Date: Thu, 20 Apr 2023 10:30:26 -0400	[thread overview]
Message-ID: <aad97313-01e4-2116-0e7f-28d41414b7a8@simark.ca> (raw)
In-Reply-To: <999c220d-dd64-d6fb-b5ef-912150a4cfd6@suse.de>

On 4/20/23 07:43, Tom de Vries wrote:
> You say you don't understand the comment, but to me it seems you do so I'm not sure I understand what your concern is.  Should the comment be improved, or do you want a change in functionality?

I just wasn't sure which username I was expected to pass to those
options, I wanted to confirm with you that the intent is to have
dedicated systems users for that.  So the comment could say that:

  It is recommended to create users on the local system that will act as
  "remote host" and "remote target", for the boards that use them.
  Pass their usernames to --host-user and --target-user.  This helps
  because:

    - remote host/target boards will use $HOME and leave (potentially
      lots of) files behind
    - it enables more strict checking of build/host/target file
      manipulations.
    - it prevents a command running on one "machine" to kill or send a
      signal to a process on another machine

> I've tried adding a bit more comments, updated version attached.

Thanks, that LGTM.

Simon

  reply	other threads:[~2023-04-20 14:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-03 15:09 [PATCH 0/1] [gdb/testsuite] Run test-case with all host/target boards Tom de Vries
2023-04-03 15:09 ` [PATCH 1/1] [gdb/contrib] Add make-check-all.sh Tom de Vries
2023-04-04 11:35   ` Andrew Burgess
2023-04-05  9:01     ` Tom de Vries
2023-04-18 12:43       ` Tom de Vries
2023-04-19 14:04         ` Simon Marchi
2023-04-20 11:43           ` Tom de Vries
2023-04-20 14:30             ` Simon Marchi [this message]
2023-04-21 15:41               ` Tom de Vries

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=aad97313-01e4-2116-0e7f-28d41414b7a8@simark.ca \
    --to=simark@simark.ca \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).