All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jul 2022, #08; Fri, 29)
Date: Sun, 31 Jul 2022 11:50:26 -0700	[thread overview]
Message-ID: <xmqqedy115hp.fsf@gitster.g> (raw)
In-Reply-To: <YuXM4pmsuDzIqbQT@coredump.intra.peff.net> (Jeff King's message of "Sat, 30 Jul 2022 20:29:22 -0400")

Jeff King <peff@peff.net> writes:

> If you get a chance before merging, can you please squash in this
> typo-fix?

Ah, sure.  

Sorry, I did see that "oops" message but didn't react to it.  Now
it's done.

Thanks.

> diff --git a/config.mak.dev b/config.mak.dev
> index b9878a4994..4fa19d361b 100644
> --- a/config.mak.dev
> +++ b/config.mak.dev
> @@ -60,7 +60,7 @@ endif
>  # uninitialized warnings on gcc 4.9.2 in xdiff/xdiffi.c and config.c
>  # not worth fixing since newer compilers correctly stop complaining
>  #
> -# Likwise, gcc older than 4.9 complains about initializing a
> +# Likewise, gcc older than 4.9 complains about initializing a
>  # struct-within-a-struct using just "{ 0 }"
>  ifneq ($(filter gcc4,$(COMPILER_FEATURES)),)
>  ifeq ($(filter gcc5,$(COMPILER_FEATURES)),)
>
> Thanks.
>
> -Peff

  reply	other threads:[~2022-07-31 18:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-29 23:18 What's cooking in git.git (Jul 2022, #08; Fri, 29) Junio C Hamano
2022-07-31  0:29 ` Jeff King
2022-07-31 18:50   ` Junio C Hamano [this message]
2022-08-01 12:01 ` ab/leak-check (was: What's cooking in git.git (Jul 2022, #08; Fri, 29)) Ævar Arnfjörð Bjarmason
2022-08-01 16:56   ` ab/leak-check 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=xmqqedy115hp.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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.