From: Gerald Pfeifer <gerald@pfeifer.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Release notes for GCC 7?
Date: Tue, 23 Aug 2016 20:20:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.20.1608232217400.14886@anthias.pfeifer.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1608231611190.6676@digraph.polyomino.org.uk>
On Tue, 23 Aug 2016, Joseph Myers wrote:
> Is there a reason there's no changes.html for GCC 7 at this point?
None, apart from me missing it and http://gcc.gnu.org/releasing.html
as well.
Segher beat me to it now (I was planning to do it tonight); let me
know whether there is anything else I can help with.
> I'd presumed that when adding new features one should also write release
> notes for them (so, I should be writing release notes for _FloatN /
> _FloatNx)
Yes, absolutely! That is the practice I always recommend.
Gerald
next prev parent reply other threads:[~2016-08-23 20:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 16:13 Joseph Myers
2016-08-23 20:20 ` Gerald Pfeifer [this message]
2016-08-24 7:35 ` Richard Biener
2017-03-12 22:45 ` PATCH for " Gerald Pfeifer
2017-03-13 8:31 ` Richard Biener
2017-03-27 8:13 ` carl hansen
2017-03-27 15:52 ` Joseph Myers
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=alpine.LSU.2.20.1608232217400.14886@anthias.pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc@gcc.gnu.org \
--cc=joseph@codesourcery.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).