All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin Ågren" <martin.agren@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Feb 2020, #05; Tue, 25)
Date: Wed, 26 Feb 2020 21:39:44 +0100	[thread overview]
Message-ID: <CAN0heSr1dEAXuU4pb=-kxSupbTT3-pKntUcgHxGGzAjRTxd8fw@mail.gmail.com> (raw)
In-Reply-To: <xmqqo8tml1lv.fsf@gitster-ct.c.googlers.com>

Hi Junio,

On Tue, 25 Feb 2020 at 23:58, Junio C Hamano <gitster@pobox.com> wrote:
> [New Topics]

> * ma/test-cleanup (2020-02-24) 3 commits
>   (merged to 'next' on 2020-02-25 at ce00c705a9)
>  + t: drop debug `cat` calls
>  + t9810: drop debug `cat` call
>  + t4117: check for files using `test_path_is_file`
>
>  Code cleanup.
>
>  Will merge to 'master'.

I had intended to reroll this topic (squashing the last two patches as
we discussed), but it looks like you beat me to it and merged this down
to next. From your review, I'm not sure that was really intended, or if
you experienced some trigger-happiness.

If you holler, I'll be happy to provide a v2, but otherwise I'll go
ahead and assume that the usual "it's in next so let's not reroll"
applies.

Martin

  parent reply	other threads:[~2020-02-26 20:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-25 22:54 What's cooking in git.git (Feb 2020, #05; Tue, 25) Junio C Hamano
2020-02-26  6:54 ` Eric Sunshine
2020-02-26 16:29   ` Junio C Hamano
2020-02-26 10:38 ` Alban Gruin
2020-02-26 16:33   ` Junio C Hamano
2020-02-26 20:39 ` Martin Ågren [this message]
2020-02-26 20:54 ` Martin Ågren
2020-02-26 21:06   ` 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='CAN0heSr1dEAXuU4pb=-kxSupbTT3-pKntUcgHxGGzAjRTxd8fw@mail.gmail.com' \
    --to=martin.agren@gmail.com \
    --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.
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.