From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 22/348] Fix -Wsahdow warnings
Date: Thu, 24 Nov 2011 04:33:00 -0000 [thread overview]
Message-ID: <CAHQ1cqEtSEUuiw_fsY5x0A9LmcvBGdAE7YGQSFFjALQj3Fd+=w@mail.gmail.com> (raw)
In-Reply-To: <CADPb22QQ196JbSZfVn13mKv7+H2E06j5XMtvC0F_R3xAt0ntFg@mail.gmail.com>
On Thu, Nov 24, 2011 at 12:56 AM, Doug Evans <dje@google.com> wrote:
> For reference sake, I did "grep -e -Wall ChangeLog*" to see what's
> been done in the past. Based on that there is room for compromise I think.
>
> Since these are just mechanical changes, and there are a lot of them,
> I'd be happy with a compromise everyone is happy (or at least
> not unhappy :-)) with.
>
> I think keeping them at the file level is easiest for you (just
> guessing though).
> And I'd be happy with a changelog entry that simply said:
>
> * foo.c: -Wshadow lint.
>
> or
>
> * foo.c (bar, baz): -Wshadow lint.
> (huey,dewey,louie): Ditto.
>
I changed(after it was pointed out that they do not conform to GNU
policy) the style of my ChangeLog entries to
* 42.c (trillian): Rename zaphod to beeblebrox(-Wshadow).
Hope this is a reasonable compromise everyone would be OK with. If
anyone have any other suggestions -- I'm all ears.
Andrey Smirnov
P.S. Just for the future reference, because English is not my first
language I expect some of the ChangeLog messages to be awkwardly
phrased. If that's the case feel free to nudge me about it and I'll
correct it(please do provide suggestions for correction).
next prev parent reply other threads:[~2011-11-24 4:33 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 13:07 Andrey Smirnov
2011-11-22 13:14 ` Eli Zaretskii
2011-11-22 13:34 ` Andrey Smirnov
2011-11-22 13:35 ` Marek Polacek
2011-11-22 14:04 ` Andrey Smirnov
2011-11-22 15:28 ` Mike Frysinger
2011-11-22 16:05 ` Joel Brobecker
2011-11-22 16:20 ` Mike Frysinger
2011-11-23 17:25 ` Doug Evans
2011-11-22 18:24 ` Tom Tromey
2011-11-23 16:46 ` Mark Kettenis
[not found] ` <CAHQ1cqFADK_pXv4JAW6ouvm_NPyM6dM+-FmVF0FojKi1rs98Wg@mail.gmail.com>
2011-11-24 3:23 ` Andrey Smirnov
2011-11-23 5:29 ` Andrey Smirnov
2011-11-23 17:06 ` Tom Tromey
2011-11-24 3:18 ` Andrey Smirnov
2011-11-23 17:56 ` Doug Evans
2011-11-23 18:03 ` Doug Evans
2011-11-23 20:16 ` Joel Brobecker
2011-11-24 4:33 ` Andrey Smirnov [this message]
2011-11-29 19:06 ` Tom Tromey
2011-11-28 15:07 ` [PATCH 022/238] [misc.] bcache.c: -Wshadow fix Andrey Smirnov
2011-11-28 15:07 ` [PATCH 024/238] " Andrey Smirnov
2011-12-20 15:46 ` Tom Tromey
2011-11-28 15:07 ` [PATCH 026/238] " Andrey Smirnov
2011-12-20 15:43 ` Tom Tromey
2011-11-28 15:07 ` [PATCH 025/238] " Andrey Smirnov
2011-12-20 15:42 ` Tom Tromey
2011-12-20 15:42 ` [PATCH 022/238] " Tom Tromey
2011-12-20 16:13 ` Andrey Smirnov
2011-12-20 19:17 ` Tom Tromey
2011-12-20 19:31 ` Andrey Smirnov
2011-12-20 21:06 ` Tom Tromey
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='CAHQ1cqEtSEUuiw_fsY5x0A9LmcvBGdAE7YGQSFFjALQj3Fd+=w@mail.gmail.com' \
--to=andrew.smirnov@gmail.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
/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