git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>,
	Glen Choo <chooglen@google.com>
Subject: Re: jk/diff-files-cleanup-fix + related un-picked-up ab/*
Date: Mon, 18 Jul 2022 10:25:54 -0700	[thread overview]
Message-ID: <xmqqfsiyqqn1.fsf@gitster.g> (raw)
In-Reply-To: <220718.86h73eyb31.gmgdl@evledraar.gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Mon, 18 Jul 2022 12:15:00 +0200")

Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:

> On Sun, Jul 17 2022, Junio C Hamano wrote:
>
>> * jk/diff-files-cleanup-fix (2022-07-12) 1 commit
>>   (merged to 'next' on 2022-07-13 at 9db5235d01)
>>  + diff-files: move misplaced cleanup label
>>
>>  An earlier attempt to plug leaks placed a clean-up label to jump to
>>  at a bogus place, which as been corrected.
>>
>>  Will merge to 'master'.
>>  source: <Ys0c0ePxPOqZ/5ck@coredump.intra.peff.net>
>
> (As noted before) that fix looks good, thanks Jeff!
>
> But here's a gentle *poke* about picking up [1], which is a related
> follow-up series (but applies directly on master).

I was excited to see a pointer and hoped that it was to another
"oops, that was stupid and this is an obvious and clean fix".  But
instead it is another "here are six patches, that is a related
follow up to the series that needed that fix on top".

I'll get to it when I have enough concentration to allow me to spot
such stupid bugs before queuing ;-)

Thanks for a ping.

  reply	other threads:[~2022-07-18 17:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18  3:14 What's cooking in git.git (Jul 2022, #05; Sun, 17) Junio C Hamano
2022-07-18  8:29 ` zh/ls-files-format (was: What's cooking in git.git (Jul 2022, #05; Sun, 17)) Ævar Arnfjörð Bjarmason
2022-07-18 10:15 ` jk/diff-files-cleanup-fix + related un-picked-up ab/* " Ævar Arnfjörð Bjarmason
2022-07-18 17:25   ` Junio C Hamano [this message]
2022-07-18 16:11 ` What's cooking in git.git (Jul 2022, #05; Sun, 17) Victoria Dye
2022-07-18 20:24   ` 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

  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=xmqqfsiyqqn1.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=chooglen@google.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. 
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).