From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <palves@redhat.com>
Cc: Simon Marchi <simon.marchi@polymtl.ca>,
Simon Marchi <simon.marchi@ericsson.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] Define GNULIB_NAMESPACE in unittests/string_view-selftests.c
Date: Wed, 09 May 2018 14:00:00 -0000 [thread overview]
Message-ID: <20180509140023.u55vt62z4mijmpf2@adacore.com> (raw)
In-Reply-To: <a91edf80-591b-b0ed-8f5a-23d50c9daa29@redhat.com>
[...]
> ... and that's what led to last year's C++ wildmatching support,
> "b -qualified", tab completion improvements, etc.
Very interesting, erm, story. Thanks for taking the time to share
it again.
> So I was waiting for gdb 8.1 (at least) to be out before proposing
> moving all of gdb to a namespace, in order to give folks a little
> time to get comfortable with the new features, and make it
> reasonable to suggest that folks upgrade their top gdb to 8.1 (a
> released version) instead of to git/trunk gdb if they want to gdb
> a bit more conveniently. That's why I was wondering whether
> now would be good time to propose moving forward with the
> "namespace gdb" approach, since 8.1 has been out for a bit.
Personally, I always use the latest and greatest, as a way of
giving it more actual-use testing. So switching now wouldn't be
a problem.
Since 8.1 is out, and we had very very very very very few bug
reports so far, I would vote for going ahead now.
--
Joel
next prev parent reply other threads:[~2018-05-09 14:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 21:25 Simon Marchi
2018-05-04 16:55 ` Joel Brobecker
2018-05-04 16:59 ` Joel Brobecker
2018-05-04 17:11 ` Pedro Alves
2018-05-04 17:24 ` Joel Brobecker
2018-05-08 20:47 ` Simon Marchi
2018-05-08 21:22 ` Joel Brobecker
2018-05-09 13:50 ` Pedro Alves
2018-05-09 14:00 ` Joel Brobecker [this message]
2018-05-09 15:19 ` Simon Marchi
2018-05-04 17:14 ` Simon Marchi
2018-05-04 17:20 ` Joel Brobecker
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=20180509140023.u55vt62z4mijmpf2@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=simon.marchi@ericsson.com \
--cc=simon.marchi@polymtl.ca \
/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