From: Olivier Hainque <hainque@adacore.com>
To: GCC Development <gcc@gcc.gnu.org>,
libc-announce@sourceware.org, binutils@sourceware.org,
cgen@sourceware.org, dejagnu@gnu.org, gdb@sourceware.org,
newlib@sourceware.org, libc-alpha@sourceware.org,
bug-make@gnu.org, bug-bison@gnu.org, m4-patches@gnu.org,
autoconf@gnu.org, automake@gnu.org, libtool@gnu.org,
bug-gnulib@gnu.org
Cc: tools-cauldron-admin@googlegroups.com
Subject: Re: GNU Tools Cauldron 2020 update
Date: Tue, 14 Apr 2020 16:20:44 +0200 [thread overview]
Message-ID: <93029E18-7747-4084-A3C1-CD952CBC7070@adacore.com> (raw)
In-Reply-To: <F3640B9A-AF61-4458-9326-0C325CA891AB@adacore.com>
Dear all,
> On 19 Mar 2020, at 15:58, Olivier Hainque <hainque@adacore.com> wrote:
>
> Dear all,
>
> With the current evolution of the COVID-19 crisis worldwide, we are
> unfortunately not in a position to maintain the organization of this
> year’s GNU Tools Cauldron as originally planned in June.
>
> We are working on the finalization of postponement options and will
> let everyone know as soon as everything is confirmed.
The uncertainties around the spread of COVID-19 are such that it
is simply not reasonable to plan an international conference at all
at this stage.
It is therefore with great sadness that we announce the cancellation
of the 2020 edition of the GNU Tools Cauldron :-(
If you have any concerns or questions, please do not hesitate to
reach out to the committee at tools-cauldron-admin@googlegroups.com.
Wishing everyone good health,
Olivier
prev parent reply other threads:[~2020-04-14 14:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 14:58 Olivier Hainque
2020-04-14 14:20 ` Olivier Hainque [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=93029E18-7747-4084-A3C1-CD952CBC7070@adacore.com \
--to=hainque@adacore.com \
--cc=autoconf@gnu.org \
--cc=automake@gnu.org \
--cc=binutils@sourceware.org \
--cc=bug-bison@gnu.org \
--cc=bug-gnulib@gnu.org \
--cc=bug-make@gnu.org \
--cc=cgen@sourceware.org \
--cc=dejagnu@gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=libc-alpha@sourceware.org \
--cc=libc-announce@sourceware.org \
--cc=libtool@gnu.org \
--cc=m4-patches@gnu.org \
--cc=newlib@sourceware.org \
--cc=tools-cauldron-admin@googlegroups.com \
/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).