public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@efficios.com>
To: gcc@gcc.gnu.org, libc-alpha@sourceware.org,
	binutils@sourceware.org, cgen@sourceware.org, dejagnu@gnu.org,
	gdb@sourceware.org, newlib@sourceware.org
Subject: Re: GNU Tools Cauldron 2019
Date: Thu, 08 Aug 2019 13:40:00 -0000	[thread overview]
Message-ID: <23d67b81-4d21-4d50-0d06-bf00ddc8f689@efficios.com> (raw)
In-Reply-To: <6b33d5a2-8113-bb9f-87a4-9180026744b6@efficios.com>

On 2019-07-25 3:13 p.m., Simon Marchi wrote:
> Hi again!
> 
> This is a little reminder about the Cauldron 2019.  If you plan on attending, please
> take a few minutes to send your registration (instructions are on the wiki [1]), it
> helps us greatly if you do it earlier than later.
> 
> Also, we have received some very interesting talk and BoF submissions, but there is
> still room available.  If you have worked on improving the GNU toolchain these past
> years, others are probably interested in hearing about it!  If you would like to
> give a talk but don't have an abstract written yet, feel free to just send the
> title/topic for now and the abstract at a later time.  We have room for full-length
> talks (~45 minutes plus questions), lightning talks (~10 minutes plus questions),
> BoFs as well as developer tutorials.
> 
> Simon
> 
> [1] https://gcc.gnu.org/wiki/cauldron2019 

Hi all,

The list of talks and BoFs for the GNU Tools Cauldron 2019 has now been published, you can consult it at:

    https://gcc.gnu.org/wiki/cauldron2019#Abstracts

Please note:

- If you have sent a registration email but did not receive a confirmation, it might have fallen through the cracks, please send it again.
- Same thing if you have sent a talk/BoF proposal and have not heard back, please send it again.
- If you have received a confirmation for your talk/BoF, but don’t see it in the list above, it’s an error, please notify me.
- If you notice a typo, a formatting problem, or would like to update the title/abstract of your talk, don’t hesitate to notify me.

If you would like to attend but haven’t registered yet, it is still time to do so.  Just follow the instructions here:

    https://gcc.gnu.org/wiki/cauldron2019#Registration

In theory, this is the last time I spam the public lists about the Cauldron (for this year!), further details about the logistics will be sent prior to the event to those who registered.

Thank you,

Simon

      reply	other threads:[~2019-08-08 13:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-14 21:28 Simon Marchi
2019-07-25 19:13 ` Simon Marchi
2019-08-08 13:40   ` Simon Marchi [this message]

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=23d67b81-4d21-4d50-0d06-bf00ddc8f689@efficios.com \
    --to=simon.marchi@efficios.com \
    --cc=binutils@sourceware.org \
    --cc=cgen@sourceware.org \
    --cc=dejagnu@gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sourceware.org \
    --cc=libc-alpha@sourceware.org \
    --cc=newlib@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).