From: Beat Bolli <dev+git@drbeat.li>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v4] Makefile: add a DEVOPTS flag to get pedantic compilation
Date: Wed, 25 Jul 2018 19:38:37 +0200 [thread overview]
Message-ID: <504f6cfe-f869-97f6-248d-642ae1e6dfc0@drbeat.li> (raw)
In-Reply-To: <xmqqzhyfuub6.fsf@gitster-ct.c.googlers.com>
On 25.07.18 18:57, Junio C Hamano wrote:
> Beat Bolli <dev+git@drbeat.li> writes:
>
>> In the interest of code hygiene, make it easier to compile Git with the
>> flag -pedantic.
>>
>> Pure pedantic compilation with GCC 7.3 results in one warning per use of
>> the translation macro `N_`:
>>
>> warning: array initialized from parenthesized string constant [-Wpedantic]
>>
>> Therefore also disable the parenthesising of i18n strings with
>> -DUSE_PARENS_AROUND_GETTEXT_N=0.
>>
>> Signed-off-by: Beat Bolli <dev+git@drbeat.li>
>> ---
>
> Hmph, what did you change between v3 and v4?
Just the commit text. In v3, it still said =No instead of =0.
>> diff --git a/Makefile b/Makefile
>> index 0cb6590f24..2bfc051652 100644
>> --- a/Makefile
>> +++ b/Makefile
>> @@ -484,6 +484,12 @@ all::
>
> The postimage of this hunk is supposed to be 11 lines long, as you
> have five additional line in the middle of 6 original context lines.
> Where did this 12 come from? I am only interested in finding out if
> our patch generation tool(s) have some bugs with this question.
>
> If this is only because you hand-edit your patch, then we have no
> tool breakage to worry about, but please refrain from doing so in
> the future (instead always go back to the commit, amend it, and
> re-run format-patch).
>
> Thanks.
You got me there :-/
Won't happen again, sorry.
>> # The DEVELOPER mode enables -Wextra with a few exceptions. By
>> # setting this flag the exceptions are removed, and all of
>> # -Wextra is used.
>> +#
>> +# pedantic:
>> +#
>> +# Enable -pedantic compilation. This also disables
>> +# USE_PARENS_AROUND_GETTEXT_N to produce only relevant warnings.
>>
>> GIT-VERSION-FILE: FORCE
>> @$(SHELL_PATH) ./GIT-VERSION-GEN
>
prev parent reply other threads:[~2018-07-25 17:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-21 20:36 [PATCH v2] Makefile: add a DEVOPTS flag to get pedantic compilation Beat Bolli
2018-07-23 18:53 ` Junio C Hamano
2018-07-24 6:04 ` Beat Bolli
2018-07-24 13:21 ` Junio C Hamano
2018-07-24 17:13 ` [PATCH v3] " Beat Bolli
2018-07-24 19:26 ` [PATCH v4] " Beat Bolli
2018-07-25 16:57 ` Junio C Hamano
2018-07-25 17:38 ` Beat Bolli [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=504f6cfe-f869-97f6-248d-642ae1e6dfc0@drbeat.li \
--to=dev+git@drbeat.li \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).