A lot of the changes are to files that GCC either imports strictly verbatim with no local changes at all, or will make changes locally to only for serious issues relating to integration with GCC; in either case, such typos cannot justify making changes locally in GCC so if you want those issues fixed you'll need to send them to the relevant upstream projects.
On Tue, 29 May 2012, Jim Meyering wrote: > sed -i '711s!Cant!Cannot","Can not","Can't!' boehm-gc/allchblk.c boehm-gc is externally maintained so such changes would need to go upstream. > sed -i '130s!RELA!Real!' gcc/config/stormy16/stormy-abi In general this looks spurious in anything dealing with ELF. > sed -i '26s!ASLO!Also!' gcc/testsuite/ada/acats/tests/a/ae3002g.ada ACATS is an external project so changes would need to go upstream. > sed -i '1s!throught!thought","through","throughout!' > gcc/testsuite/c-c++-common/pr41779.c I don't think it's particularly worthwhile fixing typos in testcases. > sed -i '323s!loosing!losing!' intl/dcigettext.c > sed -i '720s!thru!through!' intl/plural.c libintl comes from gettext so changes would need to go upstream. > sed -i '87s!relevent!relevant!' libffi/src/arm/gentramp.sh libffi is externally maintained so it's best for changes to go upstream. > sed -i '37s!truely!truly!' libgcc/soft-fp/op-common.h soft-fp is part of glibc so changes should go upstream. > sed -i '25s!sence!since","sense!' libgo/go/compress/flate/deflate.go libgo is maintained elsehwere so changes should go upstream. > sed -i '576s!sould!could","soul","should","sold!' libjava/classpath/NEWS classpath is an external project so changes should go upstream. > sed -i '5133s!Ammend!Amend!' libstdc++-v3/doc/html/ext/lwg-active.html These files are maintained by WG21 so changes should go there. > sed -i '34s!untill!until!' zlib/contrib/ada/zlib-streams.ads zlib is an external project so changes should go upstream. -- Joseph S. Myers jos...@codesourcery.com
