From: Kumar Gala <kumar.gala@motorola.com>
To: Zack Weinberg <zack@codesourcery.com>
Cc: <gcc@gcc.gnu.org>
Subject: Re: Branch created: gcc-3_3-e500-branch
Date: Wed, 16 Apr 2003 01:15:00 -0000 [thread overview]
Message-ID: <CD78B7D5-6F9D-11D7-8C8A-000393DBC2E8@motorola.com> (raw)
In-Reply-To: <87wuhva13v.fsf@egil.codesourcery.com>
Why dont you have plans to merge this branch back into 3.3? It would
seem useful to make sure that the e500 support in 3.3 was correct, and
a number of Aldy's patches that have been made to the mainline do that.
- kumar
On Tuesday, April 15, 2003, at 04:43 PM, Zack Weinberg wrote:
>
> I've just created a branch called gcc-3_3-e500-branch. On this branch
> I am going to backport the PowerPC/E500 work, done mostly by Aldy
> Hernandez, from the mainline sources to 3.3. I don't have any plans
> to merge this branch back onto 3.3, but that might make sense in the
> future.
>
> The branch will be regularly updated from the 3.3 branch. Commits
> require explicit approval from me.
>
> zw
next prev parent reply other threads:[~2003-04-15 23:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-15 22:07 Zack Weinberg
2003-04-16 1:15 ` Kumar Gala [this message]
2003-04-16 1:16 ` Zack Weinberg
2003-04-16 9:25 ` Kumar Gala
2003-04-16 16:09 ` Aldy Hernandez
2003-04-16 16:15 ` Kumar Gala
2003-04-16 16:50 ` Aldy Hernandez
2003-04-16 22:19 ` Jan Hubicka
2003-04-17 4:54 ` Zack Weinberg
2003-04-17 16:46 ` Aldy Hernandez
2003-04-17 17:28 ` Zack Weinberg
2003-05-15 4:10 ` Kumar Gala
2003-05-15 4:38 ` Zack Weinberg
2003-05-15 14:41 ` Kumar Gala
2003-05-15 15:43 ` Mark Mitchell
2003-05-15 20:14 ` Geoff Keating
2003-05-15 14:45 ` altivec testsuite Kumar Gala
2003-04-16 14:14 ` Branch created: gcc-3_3-e500-branch Gerald Pfeifer
2003-04-16 17:16 ` Zack Weinberg
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=CD78B7D5-6F9D-11D7-8C8A-000393DBC2E8@motorola.com \
--to=kumar.gala@motorola.com \
--cc=gcc@gcc.gnu.org \
--cc=zack@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).