On May 29, 2012, at 5:49 AM, Jim Meyering wrote:
> Running the following command spots over 1500 typos, and suggests fixes:
>
> $ git ls-files|misspellings -f -|grep -v '^ERROR:'|perl -pe \
> 's/^(.*?)\[(\d+)\]: (\w+) -> "(.*?)"$/sed -i '\''${2}s!$3!$4!'\'' $1/' > k
Hum, maybe a make rule (only
Joseph S. Myers wrote:
> On Tue, 29 May 2012, Jim Meyering wrote:
>
>> Running the following command spots over 1500 typos, and suggests fixes:
>>
>> $ git ls-files|misspellings -f -|grep -v '^ERROR:'|perl -pe \
>> 's/^(.*?)\[(\d+)\]: (\w+) -> "(.*?)"$/sed -i '\''${2}s!$3!$4!'\'' $1/' > k
>
>
I've applied these fixes for three miscellaneous directories with a single
typo each to fix (gcc/c-family, libmudflap, lto-plugin).
Index: libmudflap/mf-impl.h
===
--- libmudflap/mf-impl.h(revision 187979)
+++ libmudflap/mf-i
On Tue, 29 May 2012, Jim Meyering wrote:
> Running the following command spots over 1500 typos, and suggests fixes:
>
> $ git ls-files|misspellings -f -|grep -v '^ERROR:'|perl -pe \
> 's/^(.*?)\[(\d+)\]: (\w+) -> "(.*?)"$/sed -i '\''${2}s!$3!$4!'\'' $1/' > k
This command has some bugs in how
On Tue, 29 May 2012, Jim Meyering wrote:
> sed -i '8s!compability!compatibility!' config/mt-sde
> sed -i '21s!enviroments!environments!' config/stdint.m4
> sed -i '293s!arbitary!arbitrary!' config/tcl.m4
> sed -i '376s!arbitary!arbitrary!' config/tcl.m4
> sed -i '818s!apropriate!appropriate!' conf
On Tue, 29 May 2012, Joseph S. Myers wrote:
> For libjava and gcc/java changes, CC j...@gcc.gnu.org on the list (they
> may well be able to deal with the classpath typos although properly it's a
> separate project). For libstdc++-v3 changes (other than
> libstdc++-v3/doc/html/ext/ which are fi
On Tue, 29 May 2012, Jim Meyering wrote:
> sed -i '167s!Millenial!Millennial!' libgcc/config/libbid/bid128_string.c
> sed -i '30s!guranteed!guaranteed!' libgcc/config/libbid/bid64_fma.c
> sed -i '174s!oposite!opposite!' libgcc/config/libbid/bid64_fma.c
> sed -i '218s!oposite!opposite!' libgcc/conf
Joseph S. Myers wrote:
> I've applied this patch to fix what seemed to be some of the more
> straightforward cases covered by gcc/ChangeLog.
Thanks. I've run the same thing on gettext and reported the results upstream.
On Tue, 29 May 2012, Jim Meyering wrote:
> sed -i '464s!occurence!occurrence!' gcc/doc/include/texinfo.tex
> sed -i '4802s!achive!archive","achieve!' gcc/doc/include/texinfo.tex
I missed these when first listing files from upstream projects; anyway,
I've now updated texinfo.tex from upstream to
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
Arnaud Charlet wrote:
>> Also note: the line numbers listed below work for me with yesterday's
>> up-to-date trunk, but if you want to use these commands, you should rerun
>> the commands above so that the line numbers reflect your actual sources.
>> )
>>
>> This is just a heads up.
>> I'm not vol
On May 29, 2012, at 2:49 PM, Jim Meyering wrote:
> Running the following command spots over 1500 typos, and suggests fixes:
>
> $ git ls-files|misspellings -f -|grep -v '^ERROR:'|perl -pe \
> 's/^(.*?)\[(\d+)\]: (\w+) -> "(.*?)"$/sed -i '\''${2}s!$3!$4!'\'' $1/' > k
>
> The misspellings comma
> Also note: the line numbers listed below work for me with yesterday's
> up-to-date trunk, but if you want to use these commands, you should rerun
> the commands above so that the line numbers reflect your actual sources.
> )
>
> This is just a heads up.
> I'm not volunteering to make these chang
13 matches
Mail list logo
