From: Richard Earnshaw <rearnsha@arm.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Mark ARM/aarch64-branch as defunct
Date: Fri, 09 May 2014 12:24:00 -0000 [thread overview]
Message-ID: <536CC8F7.5070500@arm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 175 bytes --]
This branch existed solely to facilitate merging of the port into GCC
mainline. It's been there for a while now, so this branch is now
defunct. Marked accordingly.
R.
[-- Attachment #2: svn.patch --]
[-- Type: text/plain, Size: 1464 bytes --]
Index: htdocs/svn.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/svn.html,v
retrieving revision 1.195
diff -u -r1.195 svn.html
--- htdocs/svn.html 2 May 2014 15:32:13 -0000 1.195
+++ htdocs/svn.html 9 May 2014 12:18:46 -0000
@@ -433,12 +433,6 @@
are Dwarakanath Rajagopal <<a href="mailto:dwarak.rajagopal@amd.com">dwarak.rajagopal@amd.com</a>>
and H.J. Lu <<a href="mailto:hjl.tools@gmail.com">hjl.tools@gmail.com</a>>.</dd>
- <dt>ARM/aarch64-branch</dt>
- <dd>This branch adds support for the AArch64 architecture and will track
- trunk until such time as the port is merged into trunk. Patches to this
- branch should be tagged [AARCH64] and must be approved by ARM
- personnel.</dd>
-
<dt>cell-4_3-branch</dt>
<dd>The goal of this branch is to add fixes and additional features required
for the Cell/B.E. processor (both PPE and SPE) to GCC 4.3.x. This branch
@@ -1157,6 +1151,10 @@
by <a href="mailto:laurynas.biveinis@gmail.com">Laurynas
Biveinis</a>.</dd>
+ <dt>ARM/aarch64-branch</dt>
+ <dd>This branch added support for the AArch64 architecture and tracked
+ trunk until the port was merged into mainline.</dd>
+
<dt>ARM/hard_vfp_4_4_branch</dt>
<dd>This branch contains support for the hard-VFP variant of the AAPCS calling
standard and tracked gcc-4.4 development. This branch was maintained by
reply other threads:[~2014-05-09 12:24 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=536CC8F7.5070500@arm.com \
--to=rearnsha@arm.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).