From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Avoid spaces in osabi names
Date: Tue, 08 Mar 2016 20:59:00 -0000 [thread overview]
Message-ID: <20160308205913.GA5911@adacore.com> (raw)
In-Reply-To: <1457377364-990-1-git-send-email-palves@redhat.com>
Hi Pedro,
> gdb/ChangeLog:
> 2016-03-07 Pedro Alves <palves@redhat.com>
>
> * osabi.c (gdb_osabi_names): Avoid spaces in osabi names.
FWIW, I think this is the best compromise. The new names you chose
also look good to me.
--
Joel
next prev parent reply other threads:[~2016-03-08 20:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 19:02 Pedro Alves
2016-03-07 19:12 ` Simon Marchi
2016-03-09 1:34 ` [RFC] Remove all a.out support and gc no-longer-supported OS ABIs? (Re: [PATCH] Avoid spaces in osabi names) Pedro Alves
2016-04-19 19:26 ` John Baldwin
2016-04-20 18:50 ` Joel Brobecker
2016-04-22 13:14 ` Pedro Alves
2016-12-09 16:25 ` [pushed] " Pedro Alves
2016-03-08 20:59 ` Joel Brobecker [this message]
2016-03-09 15:58 ` [PATCH] Avoid spaces in osabi names Pedro Alves
2016-12-09 16:57 ` [PATCH] Don't allow whitespace in enum values of enum commands (Re: [PATCH] Avoid spaces in osabi names) Pedro Alves
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=20160308205913.GA5911@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/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