From: Tom Tromey <tom@tromey.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCHv3 0/3] Adding startup files to GDB
Date: Fri, 02 Apr 2021 13:20:40 -0600 [thread overview]
Message-ID: <877dlkmr1z.fsf@tromey.com> (raw)
In-Reply-To: <20210331201125.GC5391@embecosm.com> (Andrew Burgess's message of "Wed, 31 Mar 2021 21:11:25 +0100")
Andrew> With lots of help from Eli the docs are now looking good. So I'm
Andrew> planning to push this series in the new few days, unless anyone would
Andrew> like to object.
Looks good to me. Thanks for advancing this.
Tom
prev parent reply other threads:[~2021-04-02 19:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 9:48 [PATCHv2 " Andrew Burgess
2021-01-26 9:48 ` [PATCHv2 1/3] gdb: refactor the initialization file lookup code Andrew Burgess
2021-01-26 15:09 ` Simon Marchi
2021-01-26 9:48 ` [PATCHv2 2/3] gdb: process startup files and startup command line options Andrew Burgess
2021-01-26 15:22 ` Eli Zaretskii
2021-01-26 15:32 ` Simon Marchi
2021-01-26 15:30 ` Simon Marchi
2021-01-26 9:48 ` [PATCHv2 3/3] gdb: add "set startup-quietly" command Andrew Burgess
2021-01-26 15:12 ` Eli Zaretskii
2021-02-18 16:41 ` [PATCHv3 0/3] Adding startup files to GDB Andrew Burgess
2021-02-18 16:41 ` [PATCHv3 1/3] gdb: refactor the initialization file lookup code Andrew Burgess
2021-02-18 16:41 ` [PATCHv3 2/3] gdb: process early initialization files and command line options Andrew Burgess
2021-02-18 17:46 ` Eli Zaretskii
2021-03-24 12:10 ` Andrew Burgess
2021-03-24 17:17 ` Eli Zaretskii
2021-02-18 16:41 ` [PATCHv3 3/3] gdb: add "set startup-quietly" command Andrew Burgess
2021-02-18 17:32 ` Eli Zaretskii
2021-03-24 12:08 ` Andrew Burgess
2021-03-31 20:11 ` [PATCHv3 0/3] Adding startup files to GDB Andrew Burgess
2021-04-02 19:20 ` Tom Tromey [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=877dlkmr1z.fsf@tromey.com \
--to=tom@tromey.com \
--cc=andrew.burgess@embecosm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).