This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PING][PATCH] GDB/testsuite: Add a way to send multiple init commands
- From: Eli Zaretskii <eliz at gnu dot org>
- To: "Maciej W. Rozycki" <macro at codesourcery dot com>
- Cc: tromey at redhat dot com, keiths at redhat dot com, gdb-patches at sourceware dot org
- Date: Sat, 21 Jun 2014 10:14:09 +0300
- Subject: Re: [PING][PATCH] GDB/testsuite: Add a way to send multiple init commands
- Authentication-results: sourceware.org; auth=none
- References: <alpine dot DEB dot 1 dot 10 dot 1406091614210 dot 3047 at tp dot orcam dot me dot uk> <87a99jwj4u dot fsf at fleche dot redhat dot com> <alpine dot DEB dot 1 dot 10 dot 1406111821290 dot 3047 at tp dot orcam dot me dot uk> <alpine dot DEB dot 1 dot 10 dot 1406200028100 dot 3924 at tp dot orcam dot me dot uk> <83fvj0rr1q dot fsf at gnu dot org> <alpine dot DEB dot 1 dot 10 dot 1406202349410 dot 25395 at tp dot orcam dot me dot uk>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Fri, 20 Jun 2014 23:52:55 +0100
> From: "Maciej W. Rozycki" <macro@codesourcery.com>
> CC: Tom Tromey <tromey@redhat.com>, <keiths@redhat.com>,
> <gdb-patches@sourceware.org>
>
> On Fri, 20 Jun 2014, Eli Zaretskii wrote:
>
> > > > > I think this patch should also update testsuite/README to document the
> > > > > new setting.
> > > >
> > > > And presumably the old one as well, right? Cc-ing Eli for this part.
> > > >
> > > > 2014-06-11 Maciej W. Rozycki <macro@mips.com>
> > > > Maciej W. Rozycki <macro@codesourcery.com>
> > > >
> > > > * lib/gdb.exp (gdb_run_cmd): Process `gdb_init_commands'.
> > > > * lib/mi-support.exp (mi_run_cmd): Process `gdb_init_commands'.
> > > > * README (Board Settings): Document `gdb_init_command' and
> > > > `gdb_init_commands'.
> > >
> > > Ping.
> >
> > Not sure why I'm one of the addressees: there's no documentation in
> > this patch.
>
> Well gdb/testsuite/README is documentation, albeit internal only. Please
> confirm that you don't want to be bothered about it in the future.
It depends on the others: if they want me to be bothered about that, I
will. I don't want to unilaterally assume upon myself responsibility
for aspects people don't want me to.
In any case, the README path is OK. Thanks.