All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Ralf Thielow via GitGitGadget <gitgitgadget@gmail.com>,
	git@vger.kernel.org, Alban Gruin <alban.gruin@gmail.com>,
	Ralf Thielow <ralf.thielow@gmail.com>
Subject: Re: [PATCH] config.mak.dev: re-enable -Wformat-zero-length
Date: Fri, 28 Feb 2020 12:06:41 -0500	[thread overview]
Message-ID: <20200228170641.GA1405401@coredump.intra.peff.net> (raw)
In-Reply-To: <xmqqtv3aek8o.fsf@gitster-ct.c.googlers.com>

On Fri, Feb 28, 2020 at 08:42:47AM -0800, Junio C Hamano wrote:

> Jeff King <peff@peff.net> writes:
> 
> > The short of it is that we probably can't just disable the warning for
> > everybody because of portability issues. And ignoring it for developers
> > puts us in the situation we're in now, where non-dev builds are annoyed.
> 
> "git blame" unfortunately is very bad at poing at a commit that
> removed something, so I do not offhand know how much it would help
> readers who later wonder "oh, I am sure we had thing to disable
> format-zero-length warning, and I want to learn the reason why we
> dropped it", but thanks for writing this down.

I often turn to "git log -Sformat-zero" for this (and in fact that was
very useful for the research I did yesterday). But of course you have to
first _know_ about the warning and wonder "hey, didn't used ignore it?"
for that to be useful.

-Peff

  reply	other threads:[~2020-02-28 17:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-27 20:25 [PATCH] rebase-interactive.c: silence format-zero-length warnings Ralf Thielow via GitGitGadget
2020-02-27 23:54 ` [PATCH] config.mak.dev: re-enable -Wformat-zero-length Jeff King
2020-02-28 16:42   ` Junio C Hamano
2020-02-28 17:06     ` Jeff King [this message]
2020-03-03 10:17 ` [PATCH] rebase-interactive.c: silence format-zero-length warnings Alban Gruin
2020-03-03 14:20   ` Junio C Hamano

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=20200228170641.GA1405401@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=alban.gruin@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=gitster@pobox.com \
    --cc=ralf.thielow@gmail.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.