Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Simon Marchi <simark@simark.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: GNU Tools @ Linux Plumbers Conference
Date: Wed, 29 Jul 2020 14:01:24 -0700	[thread overview]
Message-ID: <20200729210124.GL8914@adacore.com> (raw)
In-Reply-To: <e7f59eb6-2192-0eb2-6b5b-9e4147ae42a8@simark.ca>

Hi Simon,

> I think it would be a great opportunity to meet in some way.  I really enjoyed
> meeting all the GDB developers who were there at Cauldron last year, I know I
> would enjoy hearing your voices again (and maybe new voices).

Me too.

> If people are interested, I don't mind taking care of registering a
> BoF session.  Keeping in mind that the deadline is this Friday (July
> 31st), I would need to know pretty quickly if at least a few others
> would show up if we do this.

I would like this.

> If we do this session, I can also take care of collecting a list of
> topics that folks would like to talk about, just post them here.  It
> can be pretty much about anything related to GDB development.

Past and planned architectural changes? E.g.
  - the moving of gnulib and gdbserver
  - some of the changes you've made to the type system to provide
    a more C++-like API (replacing some of the macros we have been
    using)
  - Do people want to give feedback on the new version numbering scheme?
  - other large changes that people would like to pre-announce?

Thanks Simon!
-- 
Joel


  parent reply	other threads:[~2020-07-29 21:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-28 15:14 Joel Brobecker
2020-07-29 20:16 ` Simon Marchi
2020-07-29 20:47   ` Jose E. Marchesi
2020-07-29 21:01   ` Joel Brobecker [this message]
2020-07-31 18:18     ` Simon Marchi
2020-07-31  4:32   ` Kevin Buettner

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=20200729210124.GL8914@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.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