From: Andreas Jaeger <aj@suse.de>
To: Peter Barada <peter@the-baradas.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Improvements for ColdFire v4
Date: Wed, 21 Jan 2004 06:39:00 -0000 [thread overview]
Message-ID: <m31xpterke.fsf@gromit.moeb> (raw)
In-Reply-To: <20040121063230.BAE17990D5@baradas.org> (Peter Barada's message of "Wed, 21 Jan 2004 01:32:30 -0500 (EST)")
[-- Attachment #1: Type: text/plain, Size: 1178 bytes --]
Peter Barada <peter@the-baradas.com> writes:
> I've got some changes kicking around that suppor the extra
> insructions and addressing modes of ColdFire v4/v4e that didn't make
> it into Bernie's previous ColdFire integration.
>
> Now that I have papers on file for GCC, which trees could my changes
> go into(GCC-3.3, GCC-3.4, CVS head)?
As always: First into CVS head. Depending on your changes, the
release manager might allow a backport to older versions.
> I'm assuming that I need to generate a ChangeLog entry as well as a
> patch against each tree? Is there a web page that describes *exactly*
Yes.
> what a submission to gcc-patches should look like(and how best to
> write a ChangeLog entry)?
There's the "Contributing" page from our main page that explains most
stuff and points to all relevant documents.
> Is it too late in the cycle(for each tree) to get these changes in?
IMHO it's too late for 3.3 and even 3.4 is rather late,
Andreas
--
Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj
SuSE Linux AG, Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
prev parent reply other threads:[~2004-01-21 6:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-21 6:36 Peter Barada
2004-01-21 6:39 ` Andreas Jaeger [this message]
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=m31xpterke.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=peter@the-baradas.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).