From: Tom Tromey <tom@tromey.com>
To: =?utf-8?Q?AlexandraH=C3=A1jkov=C3=A1?=@sourceware.org
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] remote.c: Allow inferior to reply with an error
Date: Thu, 05 Jan 2023 11:16:08 -0700 [thread overview]
Message-ID: <87tu14etjr.fsf@tromey.com> (raw)
In-Reply-To: <20230104113909.1395263-1-ahajkova@redhat.com> (=?utf-8?Q?AlexandraH=C3=A1jkov=C3=A1=40sourceware=2Eorg's?= message of "Wed, 4 Jan 2023 12:39:09 +0100")
>>>>> AlexandraHájková <AlexandraHájková@sourceware.org> writes:
> But setting the inferior's working dir is not always possible due
> to various reasons and we may not want to always stop the communication.
> This patch proposes to just warn the user in a case it wasn't possible
> to set the working dir but proceed without an error.
Thank you, this is ok.
Tom
next prev parent reply other threads:[~2023-01-05 18:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 11:39
2023-01-04 14:42 ` Eli Zaretskii
2023-01-05 18:16 ` Tom Tromey [this message]
2023-01-06 15:12 ` Andrew Burgess
2023-01-06 18:59 ` Simon Marchi
2023-01-09 12:55 ` Alexandra Petlanova Hajkova
2023-01-09 17:14 ` Tom Tromey
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=87tu14etjr.fsf@tromey.com \
--to=tom@tromey.com \
--cc==?utf-8?Q?AlexandraH=C3=A1jkov=C3=A1?=@sourceware.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).