public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@palves.net>
To: gdb@sourceware.org
Subject: GDB BoF Agenda for GNU Cauldron 2022?
Date: Mon, 12 Sep 2022 16:43:40 +0100	[thread overview]
Message-ID: <c5640457-f7b7-21b6-de09-884269d400a2@palves.net> (raw)

Hi!

Once again, we'll have a gdb BoF session in the Cauldron this year:

  https://gcc.gnu.org/wiki/cauldron2022#cauldron2022talks.the_gdb_bof

As in previous years, the intention is to discuss whatever gdb-related topics people feel like
needs discussing, hence no agenda listed in the schedule (I didn't have a list of topics in mind
when I proposed the slot).  As before, I intend to collect topics of interest at the start of the
session, and then try to cover them all.  That seems to have worked OK in the past.

However, if anyone has topics they already know they'd like to see brought up, please feel
free to let me know in advance.

Hope to see you there!

Cheers,
Pedro Alves

             reply	other threads:[~2022-09-12 15:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-12 15:43 Pedro Alves [this message]
2022-09-12 16:24 ` Luis Machado
2022-09-13 10:48   ` Luis Machado
2022-09-13 11:02     ` Tom Kacvinsky

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=c5640457-f7b7-21b6-de09-884269d400a2@palves.net \
    --to=pedro@palves.net \
    --cc=gdb@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).