public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: GCC <gcc@gcc.gnu.org>
Subject: Cauldron schedule: diagnostics and security features talks
Date: Fri, 8 Sep 2023 14:18:51 -0400	[thread overview]
Message-ID: <7db530ee-6769-5ee5-5512-1e84701a940a@gotplt.org> (raw)

Hello,

I want to begin by apologizing because I know from first hand experience 
that scheduling can be an immensely painful job.

The Cauldron 2023 schedule[1] looks packed and I noticed that Qing and 
David's talks on security features and diagnostics respectively are in 
the same time slot.  Both those sessions are likely to have pretty big 
overlaps in audience IMO since the topics are thematically related.  Is 
there a way in which they could be put in different time slots?

IIRC they were in different time slots before and were probably moved 
around to cater for another conflict (hence maybe making it harder to 
move them again) but I figured I'd rather air my request and be turned 
down than have to make the difficult choice :)

Thanks!
Sid

[1] https://gcc.gnu.org/wiki/cauldron2023

             reply	other threads:[~2023-09-08 18:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-08 18:18 Siddhesh Poyarekar [this message]
2023-09-11 11:41 ` Richard Earnshaw (lists)

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=7db530ee-6769-5ee5-5512-1e84701a940a@gotplt.org \
    --to=siddhesh@gotplt.org \
    --cc=gcc@gcc.gnu.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).