From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tromey@adacore.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
Wadud Miah <wadud.miah@nag.co.uk>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: building GDB 9.0.50.20191206
Date: Fri, 13 Dec 2019 20:21:00 -0000 [thread overview]
Message-ID: <986c3939-b6fd-b973-0ccb-1bd91f097df2@simark.ca> (raw)
In-Reply-To: <878sngvvub.fsf@tromey.com>
On 2019-12-13 3:01 p.m., Tom Tromey wrote:
> Simon> Tom, could you describe what is missing to complete this move?
>
> Completing the move of gdbsupport and then gdbserver to top-level.
Yes, I understand that doing the move is necessary to complete the move :) ? But are
there some known technical difficulties in doing it?
Simon
next prev parent reply other threads:[~2019-12-13 20:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 10:47 Wadud Miah
2019-12-12 14:10 ` Joel Brobecker
2019-12-12 14:22 ` Wadud Miah
2019-12-13 19:53 ` Simon Marchi
2019-12-13 20:01 ` Tom Tromey
2019-12-13 20:21 ` Simon Marchi [this message]
2019-12-13 23:25 ` Tom Tromey
2019-12-15 16:17 ` Tom Tromey
2019-12-17 6:01 ` Joel Brobecker
2019-12-18 20:23 ` Tom Tromey
2019-12-14 17:29 ` Christian Biesinger via gdb
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=986c3939-b6fd-b973-0ccb-1bd91f097df2@simark.ca \
--to=simark@simark.ca \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=tromey@adacore.com \
--cc=wadud.miah@nag.co.uk \
/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