From: Richard Earnshaw <rearnsha@gmail.com>
To: gcc@gcc.gnu.org
Subject: Git transition
Date: Mon, 16 Dec 2019 17:32:00 -0000 [thread overview]
Message-ID: <0DD01509-8E9F-42C2-AEC8-89A659997CE9@gmail.com> (raw)
Unfortunately a family emergency has cropped up and I can’t respond directly to the thread. I’m also unlikely to be able to follow up on this discussion in the next couple of days.
I proposed the timetable back after the Cauldron to make it clear that we were serious about moving this release cycle. However, the timetable was always a bit imprecise and we’ve already moved the final switch over date by a couple of weeks, so I don’t think slipping the decision date by a few days will impact that cut over.
So my request is please don’t rush to a decision that we might come to regret. For a halp’th of tar, and all that.
R.
reply other threads:[~2019-12-16 17:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=0DD01509-8E9F-42C2-AEC8-89A659997CE9@gmail.com \
--to=rearnsha@gmail.com \
--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).