From: Simon Marchi <simon.marchi@polymtl.ca>
To: Ambrogino Modigliani <ambrogino.modigliani@gmail.com>
Cc: gdb-patches@sourceware.org, pedro_alves@portugalmail.pt
Subject: Re: [PATCH 00/20] Fix spelling mistakes in comments
Date: Sun, 20 Nov 2016 17:30:00 -0000 [thread overview]
Message-ID: <881457a649d101c2e1c020ad08d0071e@polymtl.ca> (raw)
In-Reply-To: <1479654381-20698-1-git-send-email-ambrogino.modigliani@mail.com>
On 2016-11-20 10:06, Ambrogino Modigliani wrote:
> This series fixes number of spelling mistakes in comments in source
> code
> files in various languages.
>
> Vast majority of mistakes were discovered by a tool, however each
> mistake
> is manually checked.
>
> Ambrogino Modigliani (20):
> Fix spelling mistakes in comments in C source files
> Fix spelling mistakes in comments in configure scripts
> Fix spelling mistakes in comments in makefiles
> Fix spelling mistakes in comments in shell scripts
> Fix spelling mistakes in comments in Ada source files
> Fix spelling mistakes in comments in Assembler files
> Fix spelling mistakes in comments in Expect scripts
> Fix spelling mistakes in comments in XML files
> Fix spelling mistakes in comments in .cpu files
> Fix spelling mistakes in comments in .def files
> Fix spelling mistakes in comments in .em files
> Fix spelling mistakes in comments in .igen files
> Fix spelling mistakes in comments in .in files
> Fix spelling mistakes in comments in .inc files
> Fix spelling mistakes in comments in .l files
> Fix spelling mistakes in comments in .m4 files
> Fix spelling mistakes in comments in .opc files
> Fix spelling mistakes in comments in .sc files
> Fix spelling mistakes in comments in .tbl files
> Fix spelling mistakes in comments in .y files
Hi Ambrogino,
Thank you very much for doing this. I often stumble on small
typos/spelling mistakes and think I should fix them, but never get
around to do it. I'm really glad you took the time.
I didn't look at all the individual fixes, but in general it looks
great. It seems like patch 01/20 didn't go through the mailing list
though. Sometimes the list rejects patches because they are too big.
Did you receive a bounce mail from sourceware.org? If not, you could
try re-sending this patch by itself...
On top of the comments in the patch themselves, I have two here:
- You sent the patch to the gdb-patches@sourceware.org mailing list, but
it includes changes in other directories as well. You should add the
binutils@sourceware.org list as well, at least. I don't know if there
are other relevant lists for other sub-projects, I'll let other people
clarify this.
- You made fixes to the zlib directory. I think this is a direct copy
from the zlib project source code. It doesn't hurt to fix the mistakes
in our tree, but it would be more relevant to fix them in the upstream
project as well. Otherwise, your changes will be lost the next time we
import code from zlib. It might be the same with the readline directory
and some others, I am not sure. Others will be able to clarify this.
Thanks,
Simon
prev parent reply other threads:[~2016-11-20 17:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-20 15:06 Ambrogino Modigliani
2016-11-20 15:07 ` [PATCH 15/20] Fix spelling mistakes in comments in .l files Ambrogino Modigliani
2016-11-20 15:07 ` [PATCH 05/20] Fix spelling mistakes in comments in Ada source files Ambrogino Modigliani
2016-11-20 15:07 ` [PATCH 06/20] Fix spelling mistakes in comments in Assembler files Ambrogino Modigliani
2016-11-20 16:59 ` Simon Marchi
2016-11-20 15:07 ` [PATCH 09/20] Fix spelling mistakes in comments in .cpu files Ambrogino Modigliani
2016-11-20 15:07 ` [PATCH 03/20] Fix spelling mistakes in comments in makefiles Ambrogino Modigliani
2016-11-20 16:53 ` Simon Marchi
2016-11-20 15:07 ` [PATCH 04/20] Fix spelling mistakes in comments in shell scripts Ambrogino Modigliani
2016-11-20 15:07 ` [PATCH 14/20] Fix spelling mistakes in comments in .inc files Ambrogino Modigliani
2016-11-20 15:07 ` [PATCH 08/20] Fix spelling mistakes in comments in XML files Ambrogino Modigliani
2016-11-20 15:07 ` [PATCH 11/20] Fix spelling mistakes in comments in .em files Ambrogino Modigliani
2016-11-20 15:07 ` [PATCH 17/20] Fix spelling mistakes in comments in .opc files Ambrogino Modigliani
2016-11-20 15:07 ` [PATCH 19/20] Fix spelling mistakes in comments in .tbl files Ambrogino Modigliani
2016-11-20 15:07 ` [PATCH 10/20] Fix spelling mistakes in comments in .def files Ambrogino Modigliani
2016-11-20 15:07 ` [PATCH 16/20] Fix spelling mistakes in comments in .m4 files Ambrogino Modigliani
2016-11-20 15:07 ` [PATCH 13/20] Fix spelling mistakes in comments in .in files Ambrogino Modigliani
2016-11-20 15:07 ` [PATCH 07/20] Fix spelling mistakes in comments in Expect scripts Ambrogino Modigliani
2016-11-20 15:07 ` [PATCH 12/20] Fix spelling mistakes in comments in .igen files Ambrogino Modigliani
2016-11-20 15:07 ` [PATCH 18/20] Fix spelling mistakes in comments in .sc files Ambrogino Modigliani
2016-11-20 15:07 ` [PATCH 20/20] Fix spelling mistakes in comments in .y files Ambrogino Modigliani
2016-11-20 15:07 ` [PATCH 02/20] Fix spelling mistakes in comments in configure scripts Ambrogino Modigliani
2016-11-20 16:36 ` Simon Marchi
2016-11-20 17:30 ` Simon Marchi [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=881457a649d101c2e1c020ad08d0071e@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=ambrogino.modigliani@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro_alves@portugalmail.pt \
/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