This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
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:
pgp00000.pgp
Description: PGP signature
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |