This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [ANNOUNCE] GCC 3.3 uClinux toolchain 20030712 snapshot
- From: Dan Kegel <dank at kegel dot com>
- To: Bernardo Innocenti <bernie at codewiz dot org>
- Cc: uClinux development list <uclinux-dev at uclinux dot org>, GCC Mailing List <gcc at gcc dot gnu dot org>,CrossGCC Mailing List <crossgcc at sources dot redhat dot com>, Peter Barada <pbarada at mail dot wm dot sps dot mot dot com>
- Date: Sun, 13 Jul 2003 15:22:03 -0700
- Subject: Re: [ANNOUNCE] GCC 3.3 uClinux toolchain 20030712 snapshot
- References: <200307131946.12368.bernie@codewiz.org> <3F11A3EA.2070806@kegel.com> <200307132209.35290.bernie@codewiz.org>
Bernardo Innocenti wrote:
In order to make future reviews easier, I'm prefixing each patch
with links to the appropriate Bugzilla entries and/or mailing list
archive pages and/or description of the bug it's meant to fix.
Yes, but I need to add some more information describing the patches
in the headers. I've not written the bigger patches myself. I've
just imported them from other places.
Worth sticking on a prefix showing the effect of *not* including
the patch, even if the patch came from somewhere else...
I see you're doing the same thing on most of your patches,
but I don't see any links to Bugzilla entries. You might consider
adding them to the prologues of your patches.
Most of these are uClinux-specific problems I've found and fixed myself.
They are not in GCC's bugzilla.
Sure, but for the patches you want eventually to move into the
main gcc tree, you probably want to add entries in gcc's bugzilla...
- Dan
--
Dan Kegel
http://www.kegel.com
http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045