From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org
Subject: [wwwdocs] bugs/index.html: remove explanation of major releases
Date: Fri, 01 Dec 2017 01:18:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.21.1711301135120.3319@anthias.pfeifer.com> (raw)
We adopted a numbering scheme that clearly shows major releases
as such, so this bit has become unnecessary (and was outdated for
all pratical purposes).
Applied.
Gerald
Index: index.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/bugs/index.html,v
retrieving revision 1.120
diff -u -r1.120 index.html
--- index.html 25 Nov 2017 19:01:33 -0000 1.120
+++ index.html 1 Dec 2017 01:17:15 -0000
@@ -676,13 +676,6 @@
<a href="https://gcc.gnu.org/onlinedocs/gcc/Compatibility.html">compatibility
section</a> of the GCC manual.</p>
-<p>Remark: A major release is designated by a change to the first or second
-component of the two- or three-part version number. A minor (bug-fix)
-release is designated by a change to the third component only. Thus GCC
-3.2 and 3.3 are major releases, while 3.3.1 and 3.3.2 are bug-fix releases
-for GCC 3.3. With the 3.4 series we are introducing a new naming scheme;
-the first release of this series is 3.4.0 instead of just 3.4.</p>
-
<h4>Standard conformance</h4>
<p>With each release, we try to make G++ conform closer to the <a href=
reply other threads:[~2017-12-01 1:18 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=alpine.LSU.2.21.1711301135120.3319@anthias.pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@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).